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

With no annotations, the description carries the full burden. It discloses pricing ($0.005/call) and the default format (letter), which is useful operational context. However, it doesn't address auth requirements, rate limits, or what the response looks like (bytes vs the deliver-stored metadata), leaving meaningful behavioral gaps for a 21-param rendering tool.

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 compact sentences that are front-loaded with the core purpose; the pricing note is a useful addition. Slightly crowded by the parenthetical field list, but no real waste.

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, deeply nested rendering tool with no annotations and no output schema, the description is thin. It omits return format, error behavior (bestAttempt), and auth context. The rich schema compensates for parameter detail, but behavioral completeness is only minimally met.

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% and the schema itself thoroughly documents pdfOptions, cookies, deliver, viewport, etc. The description adds only a brief enumeration of pdfOptions fields and the letter default, which is largely redundant with the schema, so it sits at the baseline for high-coverage schemas.

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 states a specific verb (Render) and resource (URL or HTML to PDF) and names the underlying engine (Puppeteer's page.pdf()). It distinguishes itself from siblings like screenshot/markdown by producing PDF, though it doesn't explicitly contrast with them. Clear but no active sibling differentiation.

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 when-to-use guidance is given. The description does not say when to prefer this over screenshot, snapshot, markdown, or links, nor when to use url vs html (that hint lives in the schema). No alternatives or exclusions are mentioned.

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