convert_docx_to_html_with_images

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

No annotations are provided, so the description carries the full burden. While it describes the core transformation behavior, it lacks critical details like error handling, performance characteristics, file size limitations, or what happens with unsupported DOCX features. For a file conversion tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence that conveys the complete purpose without any wasted words. It's appropriately sized for a single-parameter tool and front-loads the key information.

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?

For a single-parameter tool with 100% schema coverage but no annotations and no output schema, the description adequately covers the basic transformation purpose. However, it lacks information about the output format details, error conditions, or limitations that would be important for practical usage.

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 the schema already fully documents the single parameter 'filePath'. The description doesn't add any parameter-specific information beyond what the schema provides, such as file format requirements or path validation rules.

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 specific action ('Convert'), resource ('DOCX file'), and output format ('HTML with embedded images as base64 data URIs'). It distinguishes from the sibling tool 'convert_docx_to_html' by explicitly mentioning the image embedding feature.

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 implies usage context by specifying the input format (DOCX) and output format (HTML with images). However, it doesn't explicitly state when to use this tool versus the sibling 'convert_docx_to_html' or provide any exclusion criteria or prerequisites.

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