pdf_render

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

No annotations are provided, so the description carries the full burden. It discloses the cost ($0.49 USDC) and underlying engine (Playwright), but omits details on behavior when both url and html are provided, error handling, rate limits, or output format.

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 a single sentence with a cost prefix, efficiently conveying core information. However, a slightly more structured breakdown (e.g., separate cost, action, and comparison) could improve readability.

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 lack of annotations, output schema, and parameter descriptions, the description is incomplete. It does not explain what happens when both parameters are provided, the PDF output characteristics, or any limitations, leaving significant gaps for the agent.

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?

The input schema has 0% description coverage, and the description only generically mentions 'URL or HTML' without clarifying whether they are alternatives, how they interact, or any constraints on format or size.

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 the tool converts URL or HTML to PDF using Playwright, and distinguishes itself from the sibling docconvert_pdf by claiming higher fidelity for complex pages.

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 implies a use case (complex pages needing high fidelity) via comparison with docconvert_pdf, but lacks explicit guidance on when not to use this tool or how it compares to other siblings like screenshot.

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