convert_docx_to_markdown

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

No annotations are provided, so the description must carry the full burden. It describes the conversion operation but does not explicitly state that the original file remains unchanged, mention any prerequisites (e.g., pandoc installation), or discuss error handling. For a simple read-like conversion, this is minimally adequate but could be more transparent.

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 description is extremely concise with no wasted words. It front-loads the core purpose in the first sentence and structures parameters in a clear list. Every sentence is necessary and informative.

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?

Given the presence of an output schema (not shown), the description is relieved from explaining return values. However, it lacks context on default behavior for optional parameters, supported Markdown flavor, and error handling. For a tool with many siblings, this is adequate but not thoroughly complete.

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 0%, so the description must add meaning. It provides brief explanations for all three parameters (input_path, output_path, extract_media), which adds value beyond their names. However, details like default output path behavior or extract_media format are missing, so it only meets the baseline.

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?

The description clearly states 'Convert Word document to Markdown', using a specific verb and resource. It distinguishes itself from sibling tools like convert_docx_to_pdf (different output format) and convert_markdown_to_docx (reverse direction), making its purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling conversion tools (e.g., convert_document, convert_with_pandoc_advanced), explicit context on appropriate use cases or limitations is lacking. The tool's purpose is implied but not elaborated.

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