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

Annotations already declare mutation (readOnlyHint=false), non-idempotence, and open-world access, so the bar is lower. The description adds genuinely useful context the annotations cannot convey: it is queued as a durable job, and usage billing semantics (one render.pdf per success, nothing on failure). It stops short of auth requirements or delivery prerequisites.

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 compact sentences, front-loaded with the core action and followed by the two facts an agent most needs (async job, billing). No filler.

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?

An output schema exists, so return values need no explanation, and the billing/async behavior is covered. However, with 7 parameters at 14% schema coverage on a mutation tool, the description leaves meaningful gaps about the inputs it accepts.

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 only 14%, so the description must compensate for seven largely undocumented parameters (url, html, landscape, external_id, paper_format, print_background) and it does not. It never explains the url/html exclusivity, sizes, or page-format options, leaving the schema's oneOf and defaults to speak alone.

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 names a specific verb (Render) and resource (public web page or raw HTML) with an explicit output type (PDF). This cleanly distinguishes it from siblings like render.screenshot.create and render.template.render without opening either schema.

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 (render a PDF) and the phrase 'public web page' hints at an input constraint, but no alternatives are named and no when-to-use vs render.screenshot.create, render.template.render, or render.batch.create is given. Neither is there any guidance on choosing url vs html.

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