webpage_to_pdf

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses headless-browser rendering, upload to the Papyrio API, in-memory processing with no storage, overwriting output_path, returned path and size, a 50 MB input limit, and quota consumption. These details cover side effects, data handling, output, and constraints beyond what the schema or annotations provide.

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 purpose, then usage, parameter rationale, behavior, and limits. Every sentence adds relevant operational information without repetition or wasted framing.

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 two-parameter tool with no annotations and no output schema, the description is complete: it explains what the tool does, when to use it, how inputs are processed, where output is written, what is returned, and relevant limits. No critical agent-facing context appears to be missing.

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 already 100%, so the baseline is 3. The description adds useful meaning by explaining why output_path is required for this URL-based tool and by noting that output_path will be overwritten if a file already exists.

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 and resource: fetch a public URL and render the page to PDF in a headless browser. It distinguishes the tool from PDF-oriented siblings by clarifying that it takes a URL rather than a file, so an agent can identify it without opening another schema.

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 gives clear usage context with 'Use this to archive or print a web page' and reinforces the URL-versus-file distinction. It does not explicitly name alternative sibling tools such as image_to_pdf or office_to_pdf, so it stops short of fully explicit routing guidance.

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