pdf_render_pages

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

No annotations are provided, so the description carries full burden. It correctly warns that images are untrusted, which is a behavioral trait. However, it does not disclose other behaviors like caching, performance implications, or handling of large pages beyond what the clip parameter schema describes.

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?

The description is front-loaded with a critical security warning and then states the purpose concisely. It is structured but slightly verbose due to the warning; however, every sentence serves a purpose.

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?

Given the tool's complexity and lack of output schema, the description is incomplete. It does not specify how images are returned (e.g., base64, URLs), size limits, or whether rendering respects any transformation settings. The security warning is important but does not fill all contextual 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 description coverage is 100%, so the parameter descriptions in the schema are sufficient. The tool description adds no additional information about parameters beyond the schema, meeting the baseline expectation.

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 clearly states 'Render PDF pages as PNG images,' which is a specific verb-resource pair. It distinguishes from sibling tools like pdf_read_pages by specifying image output, and adds context about untrusted data.

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 description does not explicitly state when to use this tool versus alternatives like pdf_read_pages. It provides security warnings but lacks context on scenarios where image rendering is preferred over text extraction.

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