Open the print UI, print preview or page setup

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

readOnlyHint=false correctly signals a side-effecting UI action, and the description reinforces that a real printing surface opens. The remaining content — that PrintUtils is a global rather than a module, and which helper methods exist — is implementation trivia rather than behavior an agent needs; nothing says whether the dialog blocks the session or what the call returns.

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 first and last sentences are tight and front-loaded, but the middle MEASURED paragraph about PrintUtils internals and absent methods consumes most of the text without helping tool selection or invocation.

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?

For a one-parameter UI-opening tool with no output schema and only a readOnlyHint annotation, the description covers purpose and the PDF alternative but leaves out whether the call returns immediately, whether it requires an active tab, and how the agent should proceed after the dialog opens.

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% and the single enum parameter already documents print/preview/page-setup with inline meanings. The description adds no further semantics for the action values, so the baseline of 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?

The opening sentence gives a concrete verb and resource ('Open the printing surface for a tab'), and the final sentence names the sibling it is not (browser_pdf). The middle section drifts into internal API trivia, but the core purpose is unmistakable and distinguishable from the many tab/PDF siblings.

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?

Explicitly routes the agent: 'Use browser_pdf when you want the PDF without any UI,' which cleanly separates the two paths for producing printable output. It does not state preconditions (e.g. whether a tab must be active/focused) or when-not to open the UI at all.

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