browser_click

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

Goes well beyond annotations by disclosing return values ('clicked' / 'not found'), the no-wait semantics, the ~6s failure mode with the exact error string, and a credential-based authorization gate. Annotations only cover the non-readOnly, non-idempotent, non-destructive profile; the description adds the operational detail an agent needs.

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?

Front-loads the action and mechanics, then return values, then the alternative tools, then the failure/auth caveats. Every sentence carries distinct, non-redundant information.

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, the description correctly supplies return values and failure behavior, and it covers prerequisites and the no-wait contract. Nothing essential for correct invocation is missing.

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 schema already documents that selector is a CSS selector using document.querySelector with the first match. The description adds only a light implicit note ('nothing matches') without new syntax or format guidance, so baseline 3 is appropriate.

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) on a specific resource (an element in the preview) and describes the mechanics: scroll to viewport center then fire a DOM click(). This clearly distinguishes it from siblings like browser_hover, browser_type, and browser_eval.

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 says it does not wait for the click's effects and routes the agent to browser_dom, browser_errors, or browser_frame to check outcomes. It also names prerequisites: preview must be open with agent access, and credential pages require user consent.

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