Browser PDF Export

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

With no annotations, the description carries the full burden and does well: it discloses that the PDF is written to disk rather than returned inline, that the response is a saved path plus file size, and the headless-only constraint. It omits overwrite behavior if the path exists and any permission/render-completion details, and 'Headless mode only' sits awkwardly against a schema that offers a 'connect' mode.

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 short, front-loaded sentences with zero filler; the most non-obvious fact (not returned inline) and the return shape are both stated up front.

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?

There is no output schema, so describing the return as path plus file size is necessary and present. The one gap is the unresolved relationship between 'Headless mode only' and the schema's connect/extension mode options, which an agent could find confusing.

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 100%, so the schema already documents path, format, landscape, mode, and sessionId; the description adds no syntax or format detail beyond what is there. Baseline 3 applies when structured data does the heavy lifting.

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 gives a specific verb and resource ('Render the current page to a PDF file on disk') and immediately distinguishes itself from the neighboring browser_screenshot by naming the output artifact (PDF file on disk vs. an inline image). An agent can select it without opening the 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 provides one hard usage constraint ('Headless mode only') but never says when to prefer this over browser_screenshot or how it interacts with browser_select_mode. Usage context is implied rather than stated.

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