diff --git a/skills/rhdh-jira/SKILL.md b/skills/rhdh-jira/SKILL.md
index c6dcecc..d9091a8 100644
--- a/skills/rhdh-jira/SKILL.md
+++ b/skills/rhdh-jira/SKILL.md
@@ -164,6 +164,7 @@ Load only what the current task requires.
 16. **Feature→Epic child links use Parent Link, not issuelinks.** Cross-project parent-child relationships (RHDHPLAN Feature → RHIDP Epic) use the `Parent Link` field (`customfield_10018`), not `issuelinks`. To find child Epics of a Feature, use JQL: `project = RHIDP AND type = Epic AND "Parent Link" = RHDHPLAN-XXX`. Checking `issuelinks` will show zero results and produce false "no child Epics" reports.
 17. **REST `/rest/api/3/search` returns 410 Gone.** This endpoint has been removed. Use POST to `/rest/api/3/search/jql` with body `{"jql": "...", "fields": [...], "maxResults": N}` instead. This only affects direct REST calls — `acli search` still works.
 18. **`acli workitem create` does not support `--priority`, `--component`, or `--yes`.** These flags exist on `edit`, `transition`, and `assign` but not on `create` — passing them causes "unknown flag" errors. After creating an issue, set priority, components, size (`customfield_10795`), and parent link (`customfield_10018`) together in a single `PUT /rest/api/3/issue/{key}` call.
+19. **MCP `create_jira_issue` does not support ADF.** The MCP tool's `description` parameter accepts a plain string, which Jira wraps in a single paragraph node — markdown syntax (`## Heading`, `**bold**`, `- [ ] task`) renders as literal characters. For formatted descriptions (headings, lists, code, links, task items), always use `acli jira workitem create` with `--description-file` pointing to ADF JSON. Use the MCP tool only for quick unformatted issues where plain text is acceptable.
 
 ## Error Handling