browser_save_pdf

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavioral traits: the CDP mechanism, headed/stealth compatibility, and the path-vs-base64 output split. However, it leaves gaps an agent would want before calling — what happens to an existing file at the path, what the base64 payload concretely looks like, and whether rendering is synchronous.

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?

Two tight sentences, front-loaded with the core action and mechanism, followed by the output-mode behavior. Every clause earns its place; nothing is redundant or filler.

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 there is no output schema and no annotations, the description covers the essential call decision (what it does, when it works, how output is returned) but omits details a caller might need for a professional use: the shape of the base64 return, file-overwrite behavior, and defaults for format/landscape. Adequate for a simple call, incomplete for robust use.

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 60%, with format and landscape having no schema descriptions. The description's only parameter-related content ('Saves to path, or returns base64 if path omitted') largely duplicates the path parameter's existing schema description, so it adds almost no meaning beyond the schema and does nothing to compensate for the two undocumented parameters.

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 names a specific verb ('Render') and resource ('the active page') with an explicit output format (PDF) and mechanism (CDP), which clearly scopes the operation and implicitly separates it from screenshot and blob-saving siblings. However, it does not explicitly name or contrast any sibling tool, so it falls short of full differentiation.

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?

Usage is implied: use this when you need a PDF of the current page. The note 'works in headed/stealth mode' adds a compatibility constraint that helps an agent predict success, but there is no guidance on when to prefer this over browser_take_screenshot, browser_save_blob, or other export tools, and no exclusions are stated.

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