Render PDF

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

No annotations provided; description covers the basic action (render, return signed URL) but does not disclose potential authorization requirements, rate limits, or any side effects. It implies a creation operation but lacks detail on what happens to the PDF or if files are stored.

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 sentences, under 40 words, no redundancy. Information is front-loaded with the core action and key parameters.

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?

Covers the main inputs and output (signed download URL). Missing explicit mention that template_id and html are mutually exclusive, but implied. For a tool with 3 parameters, it is reasonably complete given no output schema.

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 100%, so baseline is 3. Description reiterates the two alternatives (template_id or html) and mentions data object, but does not add significant new semantic meaning beyond the schema's own descriptions.

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 it renders a PDF using either a template_id (with reference to list_templates) or raw HTML, plus data. It distinguishes from siblings by specifying the PDF output and referencing the template discovery tool.

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?

Description explicitly mentions when to use: when rendering a PDF with either a template or raw HTML. It references list_templates for discovery but does not contrast with render_image or provide when-not-to-use scenarios. Still, clear enough for an AI to decide.

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