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

Annotations cover readOnlyHint and openWorldHint, yet the description adds real value beyond them: the download link is private and expires in 24 hours, external resources are never fetched (inline data: images only), and the call costs $0.001 via x402. Only the return/pagination specifics are left unstated.

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?

A single dense sentence front-loads the verb and resource before qualifiers, and every clause carries information (formats, page sizes, cost, security). It is packed with parentheticals but not padded.

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?

With no output schema, the description carries the return-value burden and does so — a private download link valid 24 hours — while also covering supported formats, page sizes, CSS, security posture, and pricing. An agent has everything needed to call it 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 description coverage is 100%, so all six parameters (css, title, format, filename, markdown, page_size) are already documented. The description reinforces formats, page sizes, and CSS but adds little syntax or default information beyond the schema, matching the baseline 3 for high coverage.

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 concrete verb and resource — rendering Markdown into PDF/DOCX/HTML — and enumerates the input features (tables, code, lists, headings) and output variants. No sibling (extract_tables, get_document, screenshot) does document rendering, so the scope is unambiguous.

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?

Usage is implied by the description (render Markdown to a document format) and the cost/format notes help selection, but there is no explicit when-to-use or when-not-to-use guidance and no alternative tool named. Adequate but leaves the agent to infer context.

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