browser_print_to_pdf

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing behavioral: it does not say whether the write is to disk, whether the page must be fully loaded first, what permissions are needed, or what the tool returns on success. For a file-writing operation with zero annotation coverage this is a notable gap.

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?

A single short front-loaded sentence with no filler or redundancy. It is efficient, though the terseness is part of why so much behavior goes unexplained.

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 annotations, no output schema, an undocumented parameter, and no explanation of return value or side effects, the definition is too thin for a tool that writes a file to a caller-supplied path. An agent cannot tell what happens on success or on an invalid path.

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 only 50% — save_path is documented in the schema while landscape is undocumented in both places. The description mentions no parameters at all, so it adds nothing to compensate for the uncovered 'landscape' option or explain path format/overwrite behavior.

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+resource ('Print the current page to a PDF file'), which is clear and distinguishes it from the many non-file-producing siblings. It does not, however, explicitly contrast itself with browser_screenshot, the nearest alternative, so it stops short of a 5.

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 when-to-use guidance is given and no alternative is named, even though browser_screenshot is an obvious overlapping sibling that an agent would need to disambiguate against. The only implicit signal is that this tool produces a PDF file rather than an image.

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