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

Annotations already cover the safety profile (non-read-only, non-destructive), and the description adds meaningful behavioral context: the conversion engine is LibreOffice, only file uploads are supported, and remote URLs are not fetched. This goes beyond the schema and annotations without contradicting them.

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 with the core purpose first, followed by the most important constraint (file upload only) and a category tag. Every element earns its place with no wasted words.

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 no output schema, the description is complete: it states what is converted, the engine used, the input form, and the key exclusion. The schema covers the remaining file details, so an agent has enough information to invoke this tool correctly.

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 coverage is 100% for the single file parameter, so the baseline is 3. The description adds value by clarifying that the parameter must be an uploaded file, not a URL, and reinforces the accepted extensions and size constraint already present in 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?

The description states a specific verb ('Convert') and resource ('HTML file .html or .htm to PDF'), and immediately distinguishes itself from URL-based conversion tools by declaring 'File upload only — URLs are not fetched.' This is precise and clearly separates it from siblings like convert_url_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 provides clear usage boundaries: only local HTML file uploads are accepted, and URLs are explicitly excluded. It does not name the sibling alternative, but the URL exclusion effectively tells an agent when not to use this tool and implies the alternative for URL input.

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