browser_click

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

Annotations already mark the tool as destructive (destructiveHint=true) and not read-only (readOnlyHint=false). The description adds no behavioral context beyond this—e.g., no mention that clicks can trigger navigation, open dialogs, or submit forms. The doubleClick parameter is not explained in the description.

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 only six words, which is highly concise. However, the extreme brevity sacrifices important information, making it less effective despite lacking fluff.

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?

Given the lack of an output schema and the tool's potential destructiveness, the description fails to explain how targets are obtained, what double clicking does differently, or how modifier keys affect behavior. With many sibling tools, more context is needed for correct selection.

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 the baseline is 3. The description does not provide any additional meaning beyond the schema; it repeats 'click' without detailing parameter usage or relationships (e.g., how 'target' relates to the snapshot).

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 states 'Perform click on a web page', which clearly identifies the action (click) and target (web page). It distinguishes from coordinate-based clicks (browser_mouse_click_xy) but does not explicitly differentiate from other interaction tools like browser_hover or browser_type.

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?

No guidance is provided on when to use this tool versus alternatives such as browser_mouse_click_xy, browser_hover, or browser_type. It does not mention prerequisites (e.g., needing a page snapshot), exclusions, or contextual triggers like form submission.

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