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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real behavioral facts on top: a 30-credit cost, a download link valid for 2 days, and that the response includes the resulting page count. The paid-plan gating of pageRanges/landscape is also disclosed, which an agent could not infer from the schema defaults.

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?

Front-loaded with the core action and formats, then cost and return details. It is dense but every clause carries information; the only mild redundancy is restating the title verbatim at the start.

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 three-parameter conversion tool with a full schema and output schema, the definition covers cost, output artifacts (link, page count, validity window), and plan gating — everything needed to invoke it correctly and set expectations.

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%, so the baseline is 3; the description earns an extra point by clarifying that pageRanges and landscape only apply on paid plans, which is conditional semantics absent from the schema itself.

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?

States a specific verb and resource (converts Word/Excel/PowerPoint/OpenDocument/RTF/text/CSV files to PDF) and enumerates the exact input formats, so an agent can tell it apart from HTMLtoPDF, WebsitetoPDF, MarkdowntoPDF or PDFtoImage purely from the description.

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?

Gives clear operating context: upload the file or send its URL, and note that selected pages and landscape orientation are gated to paid plans. It does not explicitly name the sibling converters (HTMLtoPDF, WebsitetoPDF) or say when to prefer them, so it stops short of full when/when-not routing.

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