browser_pdf

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

The description discloses that the operation returns a Base64-encoded PDF, which is a key behavioral aspect. However, it does not explicitly state whether the operation is read-only or if any side effects occur, though export implies no page modification. Since no annotations are present, more detail would improve 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 a single concise sentence that conveys the essential purpose. No superfluous words or redundancy.

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?

The description covers the main functionality and output format, and all parameters are described in the schema. It does not mention error handling or edge cases, but for a simple export tool it is sufficiently complete.

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?

All three parameters (scale, format, landscape) have descriptions in the schema, so coverage is 100%. The description does not add additional semantics beyond the schema, e.g., valid ranges or interactions between parameters, so it stays at the baseline.

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 identifies the action (export), the resource (current page), and the output format (PDF with Base64 encoding). It differentiates from siblings like browser_screenshot by specifying PDF, making its purpose unambiguous.

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 does not specify when to use this tool versus browser_screenshot or browser_export. No conditions or alternative comparisons are provided, so an agent lacks guidance on selection.

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