print_page

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

readOnlyHint=true already declares the safety profile, and the description adds that a PDF file is written and its path returned. It notes the write-to-disk side effect ("Returns the saved file path") but does not describe default output location, overwrite behavior, or whether the file is created synchronously; the file-creation side effect sits in mild tension with readOnlyHint but does not clearly contradict it.

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 short, front-loaded sentences with zero filler; the action comes first and the return value second. Nothing is repeated from 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?

With no output schema, stating the return value (saved file path) is a useful addition, and all parameters are covered by the schema. However, for a tool with a near-identical sibling, the description omits any routing guidance or notes on when the PDF is generated, leaving a meaningful gap.

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 100%, so saveTo, landscape, and background are fully documented in the schema with defaults and path-resolution rules. The description adds no parameter meaning beyond what the schema already provides, so the 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 ("Print the current page to a PDF file") plus the mechanism ("using print CSS"), so an agent knows exactly what is produced. It does not explicitly differentiate itself from the sibling screenshot_page, leaving the PDF-vs-image distinction to inference.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the closely related screenshot_page alternative. The agent must guess whether to print or screenshot based on the name alone.

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