Markdown to Word (.docx)

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description is unusually rich about behavior — RTL auto-detection, default Calibri, default output name derived from the title/first heading, HTML dropped, images not embedded — far beyond what the annotations state. However, it explicitly says 'Writes the .docx to "output"', which conflicts with the declared readOnlyHint=true; an agent trusting the annotation could be misled about filesystem side effects. The description itself is not misleading, but the conflict with structured metadata caps this dimension.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The core operation and scope are front-loaded in the first clause, followed by a dense but scannable feature inventory. It is long, and the feature list could be compressed, but essentially every clause carries information an agent cannot get from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero required parameters and no output schema, the description does the important work: it tells the agent that one of markdown/path must be supplied and explains where the file lands. It does not describe the tool's response payload (beyond the returnBase64 option), which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the nine parameters is already documented; the description only restates a few (title/author as document properties, font default Calibri, fontSize, rtl "auto"). It adds the useful default-file-name rule tied to title/first heading, but returnBase64 and the output path semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a precise verb+resource+output ('Convert Markdown (GitHub flavoured) to a real Word .docx') and enumerates the exact constructs handled. It is trivially distinguishable from siblings such as ai_markdown_to_pdf and ai_docx_to_markdown, which go the other direction or to another format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the two accepted input modes ('Give "markdown" inline or "path" to a .md file') and the two non-conversions (images not embedded, raw HTML dropped), which lets an agent judge fitness. It never explicitly names when to prefer ai_markdown_to_pdf or ai_docx_to_markdown, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.