browser_pdf

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

No annotations provided. The description does not explain what happens with the generated PDF (e.g., downloaded, file path, returned) or mention side effects. It only lists parameter descriptions without behavioral context beyond the action.

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?

Description is concise and front-loaded with the main action. The Args section is structured and clear, though slightly redundant with the schema.

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?

Despite having an output schema, the description omits important context: where the PDF is saved, whether it's returned in the response, and any file naming conventions. This lack of completeness forces the agent to infer behavior.

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 coverage is 0%, so description must add meaning. It briefly describes each parameter (page_id as target, format options, print_background as include background graphics) but lacks detail on default values and exact format specifications.

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 'Save the current page as a PDF file' clearly states the verb and resource, distinguishing from sibling tools like browser_screenshot (image) and browser_read_page (text).

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?

No guidance on when to use this tool vs alternatives like browser_screenshot or browser_read_page. The description does not mention any prerequisites or use cases.

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