Save as PDF

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

With no annotations, the description must carry the behavioral burden; it usefully discloses the default save location (Downloads), the naming convention (page title), and that the screen/window is unaffected. It omits other operationally important behavior: whether a save/download dialog can appear, whether the call waits for completion, and overwrite handling for an existing file.

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 tight sentences: what it does, the default-path fallback, and the non-disruptive guarantee. Front-loaded and every sentence carries information an agent needs.

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 five-parameter save tool with only one required parameter and no output schema, the description covers the essential behavior and the most likely agent question (where did the file go). It stops short of describing the return value or failure modes, a minor gap rather than a blocking one.

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 baseline is 3, but the description adds real value by defining the semantics of an omitted path (fall back to Downloads, name after the page title) — behavior the schema's path description does not state. The tab/agent/multiSlot parameters are left entirely to the schema, which is acceptable given full 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?

States a specific verb and resource ("Saves the page as a PDF") with concrete examples (receipts, articles) that pin down the artifact type. This cleanly separates it from the image-producing browser_screenshot and the wait-only browser_download_wait sibling without needing 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?

The description implies when to use it (when you want a durable PDF of the current page) and explains the path-omitted case, but it never explicitly contrasts with browser_screenshot or browser_download_wait, nor states prerequisites. Usage is inferable rather than directed.

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