convert_html_to_docx

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It only mentions the return type ('Output path or error message') but does not disclose side effects (e.g., file overwriting) or dependencies (e.g., pandoc).

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 a clear purpose statement followed by parameter and return descriptions. Every sentence provides necessary information without extraneous content.

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 tool's simplicity and the existence of an output schema, the description covers the essential purpose, parameters, and return type. It is sufficient for correct invocation, though it could mention potential error conditions or default output path behavior.

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?

With 0% schema coverage, the description adds meaningful one-line explanations for all three parameters (input_path, output_path, reference_doc). It clarifies their roles beyond the schema titles, though it could detail default behaviors when optional params are omitted.

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 the tool converts HTML to a Word document, with a specific verb ('Convert') and resource ('HTML to Word document'). It is distinct from sibling tools like convert_markdown_to_docx or convert_html_to_pdf.

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 does not provide when to use this tool versus alternatives like convert_markdown_to_docx. It does not mention prerequisites (e.g., pandoc) or any exclusions, relying on implied usage.

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