browser_pdf_save

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

The description discloses that the tool saves to PDF and returns a file path, which is basic behavior. With no annotations provided, it lacks details about side effects, permissions, or error conditions, which limits transparency.

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 extremely concise with two short sentences, both front-loaded with essential information. No superfluous words.

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 the low schema coverage and no annotations, the description is incomplete. It does not specify prerequisites (e.g., a loaded page), the exact meaning of 'Chromium only', or details about the return value, leading to potential misuse.

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?

The schema coverage is 0%, and the description does not explain the 'output_path' parameter (e.g., required format, default directory) or the 'session_id' parameter (e.g., when it is needed). This leaves the agent without crucial usage details.

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 clearly states the tool saves the current page as a PDF file, which is a specific verb+resource. However, it does not distinguish from sibling tools like 'browser_screenshot' or 'browser_capture_mhtml', leaving potential ambiguity.

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 mention of 'Chromium only' provides a usage constraint but there is no explicit guidance on when to use this tool versus alternatives, nor what happens if not in a Chromium session.

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