browser_mouse_move_click

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

The description adds little beyond the annotations. It states the tool moves and clicks but does not disclose that clicking is optional (despite the schema default), nor does it describe the coordinate system, potential side effects, or event behavior. The destructiveHint annotation is present, but the description does not elaborate on what destructive consequences might occur.

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 with no filler, making it highly concise and front-loaded. While it lacks depth, it is appropriately brief for a simple tool, though a bit more context could be added without hurting conciseness.

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 existence of sibling tools like browser_click and browser_hover, the description does not provide enough context to distinguish when this tool is the right choice. It omits the optional nature of clicking, the coordinate reference frame, and return behavior, making it under-specified for reliable 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?

The input schema provides 100% coverage of parameter descriptions, including x, y, click, and button. The description merely adds 'target coordinates' without providing extra meaning or clarifying edge cases, so it meets the baseline but adds little value.

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 identifies the tool as controlling fine mouse movement to specific coordinates and potentially clicking there. It distinguishes itself from browser_hover and browser_click by emphasizing coordinate-based movement, though it doesn't explicitly state that the click is optional, which could cause minor ambiguity.

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_click or browser_hover. The description does not include any context about suitable scenarios, prerequisites, or exclusions.

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