browser_click

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

The description adds the constraint that the element must be from the current browser_snapshot and that coordinates are viewport-based, which complements the annotations. However, it does not disclose post-click behavior (e.g., navigation, page changes) or the meaning of wait_ms, leaving some behavioral aspects undocumented beyond the destructiveHint annotation.

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 description is two concise sentences, front-loaded with the action and resource, and every word adds value. No redundancy or filler.

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?

The tool has no output schema, and the description does not mention what the tool returns or what observable effect occurs beyond clicking. Given the destructive annotation and the need to coordinate with browser_snapshot, more detail about wait_ms and post-click state would be necessary for complete understanding.

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?

With 0% schema description coverage, the description must explain all parameters, but it only clarifies element_id and x/y. The wait_ms parameter is not described at all, leaving the agent to infer its purpose from the default value alone. This is a significant gap for a 4-parameter tool.

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 description uses a specific verb 'Click' with a resource 'a current browser_snapshot element_id', clearly distinguishing it from sibling tools like browser_type or browser_scroll. It also clarifies the coordinate fallback, leaving no ambiguity about the tool's core function.

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?

It explicitly instructs to use viewport coordinates only when no semantic element reference is available, providing a clear when-to-use rule for the two input modes. However, it does not compare against sibling tools like browser_select or browser_press, so it stops short of full alternative guidance.

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