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

With no annotations, the description carries the full burden. It usefully discloses the cost model ($0.005/call, 3 free calls/day without an API key) and defaults, but says nothing about permissions, failure/timeout behavior, or that output can be bytes or stored metadata (covered only by the schema's deliver param).

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 sentences, front-loaded with the core action and options, then the pricing detail. Efficient with no filler, though the parenthetical option list borders on redundant with the schema.

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 21-parameter tool with nested objects, no annotations and no output schema, the description is thin. The pricing note is a genuine addition, but it omits any mention of the bytes-vs-metadata delivery choice, error handling, or prerequisite auth, leaving notable gaps.

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 76%, so the schema already documents most parameters well (defaults, ranges, formats). The description merely re-lists a subset of pdfOptions (format, scale, margins, templates, printBackground, pageRanges) that the schema already covers, adding no meaning beyond it.

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 (render) and both resource types (URL or HTML) producing a PDF, with the mechanism named (Puppeteer page.pdf). It is clear what the tool does, though it does not explicitly differentiate itself from siblings like screenshot or markdown.

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?

No guidance on when to choose this tool over the sibling rendering tools (screenshot, markdown, snapshot, links). The url-vs-html exclusivity lives in the schema, not the description, so there is essentially no usage routing here.

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