Export the page as PDF

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

Annotations only declare readOnlyHint=true; the description adds substantial context beyond that — output is binary base64, may be large, and should be written to a file, with an observed format marker (%PDF-1.4). It does not cover pagination, paper size defaults, or whether rendering is awaited before capture.

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 sentences, each doing distinct work: what it does and returns, how it differs from the screenshot sibling, and a practical caveat about output size. Core action and return format are front-loaded.

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?

With no output schema, the description correctly carries the return-value burden (base64 PDF, potentially large). Combined with 100% parameter coverage, the only real omission is routing guidance against browser_print.

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 three parameters (context, landscape, printBackground) are already fully documented with defaults. The description adds no syntax or behavioral detail about them, so 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?

States a specific verb and resource ('Render the page to PDF and return it base64-encoded') plus the return encoding, and explicitly contrasts scope with browser_screenshot. An agent can identify the tool without opening 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?

Gives a clear selection rule: use this for full-document capture, use browser_screenshot for viewport capture, and it names the long-page case explicitly. It does not, however, address the closely related browser_print sibling, leaving one plausible alternative un-disambiguated.

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