convert_to_docx

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

Excellent disclosure beyond annotations: details side effects (writes binary to disk, creates directories, overwrites files), explains dual return modes (JSON confirmation vs JSON binary-guidance with base64_preview), and clarifies the re-call pattern when output_path is omitted. Complements annotations (readOnly=false, destructive=false) with specific I/O behavior.

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?

Well-structured progression: purpose → output characteristics → side effects → return values → usage comparisons. Each sentence provides distinct value. Minor verbosity in return value explanation could be tighter, but front-loading is strong and scannable.

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?

Despite no output schema, comprehensively documents both return structures (write-confirmation and binary-guidance objects). Adequately covers binary conversion complexity, file system interactions, and sibling tool landscape. No gaps given the tool's scope.

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 has 100% coverage with detailed parameter descriptions. Description adds critical usage context beyond schema: emphasizes that output_path is nearly mandatory for binary formats and explains the functional difference between providing vs omitting the parameter. Slight deduction for not adding semantic nuances to the 'markdown' parameter beyond schema definition.

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?

Clear specific verb ('Convert') with source and target resources (Markdown to DOCX). Explicitly distinguishes from 21 sibling conversion tools by specifying 'Word-compatible documents' and contrasting with RTF, PDF, and HTML alternatives.

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?

Provides explicit guidance on when to use ('Word-compatible documents') and clear alternatives ('Prefer convert_to_rtf for legacy... convert_to_pdf for read-only... convert_to_html for web'). Also specifies critical behavioral guidance that 'output_path should almost always be provided' for binary formats.

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