render_pdf

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

With no annotations, the description carries the behavioral disclosure burden. It usefully mentions that 'PDF bytes are not inlined' and that only size info is returned, which is a non-obvious output trait. However, it does not explain how the PDF is delivered (e.g., file reference, URL), whether rendering is synchronous, or any resource limits.

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 tight sentences with no filler. The primary purpose is front-loaded, and the important output behavior ('bytes are not inlined') is stated efficiently in the second sentence.

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 no output schema and no annotations, the description should explain return values clearly. It mentions size info and non-inlined PDF bytes, but omits how to access the actual PDF file, which is critical for an agent to use the result. It also lacks any guidance on file size limits, timeout behavior, or whether the rendered PDF is persisted.

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 71%, so the schema already documents most parameters. The description adds little parameter-level meaning beyond the schema; for example, 'or raw HTML' mirrors the html parameter description. Margin and landscape remain undocumented in both schema and description, leaving minor gaps.

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: 'Render a web page (or raw HTML) to a print-ready PDF file.' It clearly distinguishes the tool from siblings like render_screenshot by specifying PDF output, and clarifies the two valid input modes (URL or raw HTML).

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?

No explicit guidance is given about when to use this tool versus alternatives such as render_screenshot, extract_page, or ai_extract. The description implies PDF-related use cases but does not state exclusions or name sibling tools for comparison.

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