Generate a PDF from a public URL

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

With no annotations provided, the description carries the full burden. It discloses the output type (download URL), the one-hour validity, and the public-URL restriction. It does not mention error handling, timeouts, or rendering limitations, but these are not critical for a straightforward URL-to-PDF conversion. This is better than a bare 'Generate PDF from URL'.

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 two concise sentences, front-loading the primary action and output. It avoids unnecessary details and earns every word, making it easy for an agent to parse quickly.

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?

The description covers the core flow (load page, render PDF, return temporary URL) and explicitly mentions the one-hour validity, which is essential context absent from the schema. It does not describe failure modes or rate limits, but given the rich schema and simple interface, this is reasonably complete. The lack of an output schema is compensated by the description of the return value.

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 the baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter. The optional formatting parameters (format, margin, landscape, etc.) are adequately documented in the schema and the description doesn't add context about their interactions.

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 uses a specific verb-resource pair: 'loads a public web page and renders it to PDF' and clearly states the output (download URL). It distinguishes from the sibling tool 'generate_pdf' by explicitly naming the input source (public URL) and the output behavior.

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?

It provides a clear constraint ('Only public http/https addresses are allowed') which informs the agent about valid inputs, but it does not explicitly state when to use this tool vs the sibling 'generate_pdf' or mention any alternative usage scenarios. The guidance is mostly about prerequisites, not comparative usage.

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