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

Annotations already provide readOnlyHint, idempotentHint, and safety signals. The description adds that a URL source is required and custom page size/orientation are available, but it does not disclose the output format (PDF binary or URL), synchronous nature, or file size limits. It adds some value beyond annotations but lacks depth.

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?

Three sentences, each serving a clear purpose: action + inputs, URL requirement, custom options. No filler. Front-loaded with the most critical 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?

Given the presence of a full input schema, annotations, and an output schema (implied), the description covers the core functionality. However, it lacks explicit mention of the output format (PDF binary or URL) and does not address potential limitations like file size. Slightly more context could improve completeness.

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?

The schema has 100% parameter description coverage, so the description is not required to add much. It reiterates the supported formats and mentions page size/orientation, but does not enhance understanding beyond what the schema already provides. Baseline 3 is appropriate.

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 action (Convert to PDF) and lists many specific input formats (DOCX, XLSX, PPTX, HTML, etc.). It distinguishes from siblings like 'document.convert.from_pdf' (PDF to other formats) and 'document.convert.web_to_pdf' (webpage to PDF) by focusing on file conversion with a URL source.

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 implicitly groups formats but does not explicitly tell when to use this tool versus siblings like 'document.pdf.from_html' or 'document.convert.web_to_pdf'. No when-not or alternative guidance is provided, though the listed formats and context of siblings offer some inference.

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