browser_mouse_click

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

With no annotations, the description carries the full burden. It only states the action without disclosing side effects (e.g., triggering navigation, waiting for page load), error conditions (e.g., out-of-bounds coordinates), or whether clicks are asynchronous. It adds no behavioral context beyond the name.

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 a single sentence, concise and front-loaded with the core action. However, it relies on a reference to browser_docs instead of providing essential details, slightly reducing efficiency.

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 browser automation tool, the description is incomplete. It lacks information about return values, synchronous/asynchronous execution, waiting behavior, and whether coordinates must be within the viewport. Given no output schema or annotations, it leaves significant gaps.

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?

Parameter descriptions are fully covered by the schema (100%), which adequately explains x, y, button, and clickCount. The tool description adds no additional meaning, so it meets the baseline but does not exceed it.

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 clearly states that the tool clicks the mouse at specific coordinates or current position, using the verb 'Click'. It distinguishes from siblings like browser_hover and browser_mouse_drag, but does not differentiate from the similarly named browser_click, causing potential confusion.

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 like browser_hover or browser_click. There is no mention of prerequisites (e.g., page loaded, element present) or when to prefer coordinate-based vs current position clicks. The reference to browser_docs is vague.

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