Save as PDF

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

The description is consistent with annotations (readOnlyHint=true, destructiveHint=false) — saving a PDF does not mutate page state. It adds the 'current page' scoping constraint beyond the annotations, but does not disclose output-file behavior (where the file lands, overwrite semantics, or any confirmation). Annotations carry the safety profile; the description adds modest scope context.

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?

A single efficient sentence with zero waste, directly stating the operation and its scope. Nothing extraneous.

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 low-complexity save tool with zero required parameters, 100% schema coverage, and no nested objects or output schema, the description plus schema is nearly sufficient. The only gap is the absence of any statement about the return value or file-handling outcome, which is minor for a simple print-to-PDF operation.

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 all five optional parameters (scale, format, filename, landscape, printBackground) are already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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 ('print') and resource ('current page'), clarifying that the operation exports the currently-loaded page to a PDF. This differentiates it from image-based siblings like browser_take_screenshot, though it does not explicitly name that sibling. It's clear but leaves sibling differentiation implicit.

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?

Usage context is implied — an agent would select this when it needs a PDF export of the current page — but the description gives no explicit when-to-use/when-not guidance and does not reference alternatives such as browser_take_screenshot for image output. Adequate but relies on inference.

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