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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds real behavioral context beyond them: per-page pricing, a USDC per-call cost, and the pagination model ('max_pages up to 50, default 10; continue with first_page'). This is useful cost and continuation info an agent would otherwise lack.

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?

Two dense sentences, front-loaded with the purpose and constraint range before the pricing. Every clause carries information, though the two cost statements ('$0.008 + $0.001 per page' and '$0.058 USDC per call') sit awkwardly together and could read as inconsistent.

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 9 parameters at 89% coverage and no output schema, the description supplies the cost, DPI range, and pagination model that matter for correct invocation. It omits any mention of the output shape (base64 vs share links) and the url-vs-base64 input choice, which the schema carries but the agent must still reconcile.

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 already 89%, so the baseline is 3, but the description adds meaning the schema does not: the 50-300 dpi operating range and the 'continue with first_page' pagination semantics. It does not clarify the url vs file_base64 source choice or the store/base64 output behavior.

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+resource+output ('Render PDF pages to PNG or JPEG at 50-300 dpi'), so the agent immediately knows what the tool produces. It does not name or differentiate itself from close siblings like pdf, pdf_tools, doc_convert, or image_convert, so it falls short of a 5.

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 parenthetical '(for vision models, previews or thumbnails)' implies intended use cases but never states when to prefer this over pdf_tools/image_convert or when not to use it. Usage is implied rather than explicitly routed.

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