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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety bar is lower, but the description still earns credit by naming concrete consequences — submitting forms, purchasing items, deleting data — which tells the agent exactly what irreversible side effects to guard against. It stops short of saying whether the click waits for navigation or accepts confirm dialogs.

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: the first front-loads what the tool does and its two targeting modes, the second carries the risk warning. No filler, though it could have folded in the browser_find prerequisite it hints at.

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 annotations covering the safety profile and an output schema present, the description only needs to convey purpose and risk, which it does. Missing only the explicit relationship to browser_find/browser_tabs for locating targets, which the schema descriptions partially supply.

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 each parameter (selector, browser_text, device, target_id, timeout_ms) is documented in the schema itself. The description only echoes the selector/visible-text distinction already present in the schema, adding no format or precedence guidance beyond it, 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 (click) plus resource (an element on the current Chromium page) and both targeting mechanisms (CSS selector or visible text). It distinguishes itself from generic click tools like ui_click/computer_click by scoping to the Chromium page and CSS selectors, though it never names those siblings explicitly.

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 precondition ("Inspect the tab and target first") and implies the element must already be verified, likely via browser_find, but never names browser_find, browser_snapshot or any alternative tool or the condition that would select them. Usage is implied rather than spelled out.

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