save_pdf

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does this well by revealing atomic file writes, validation of non-empty PDF bytes, and the CDP timeout behavior that invalidates and detaches the debugger lease.

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 dense sentences with no filler. Purpose is front-loaded, and every clause adds meaningful behavioral or safety information.

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?

While an output schema exists and the behavioral detail is strong, the tool has 8 parameters, no annotations, and no schema descriptions. Missing context includes prerequisites like an active tab or session, timeout units, and clearer guidance for optional parameters, so the description is not fully complete for correct invocation.

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 0%, and the description adds no parameter-level explanation for save_path, session_id, timeout units, page_ranges, or the other options. Parameter names and defaults provide some clues, but the description does not compensate for the low coverage.

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 ('Print') with a clear target ('real-browser tab') and a specific output ('validated PDF file'). It is clearly distinct from sibling screenshot and download tools, even without naming them.

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?

The intended use is implied: call this when you need to turn the current real-browser tab into a PDF. However, it does not explicitly mention when not to use it or name alternative tools, leaving some routing to inference.

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