browser_mouse_move_xy

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

Annotations indicate destructiveHint=true and readOnlyHint=false, suggesting the move could trigger side effects (e.g., hover events, CSS changes), but the description does not explain what happens upon moving the mouse (events triggered, visual feedback, error conditions). It adds no behavioral context beyond the annotations.

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 one short sentence with no unnecessary words. It is concise, though it sacrifices some completeness. It earns a high score for being front-loaded and efficient.

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 output schema and the presence of many sibling mouse tools, the description is incomplete. It does not specify whether the move is absolute or relative, whether it triggers mouse events, or what happens if coordinates are out of bounds. Additional context would help an agent use this tool correctly.

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 description coverage is 100% (both x and y have 'X coordinate' and 'Y coordinate' descriptions), so the baseline is 3. The tool description adds no extra parameter context such as coordinate system (viewport vs page), units (pixels), or valid ranges, but it does not need to compensate since the schema is sufficient.

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 'Move mouse to a given position' clearly states the action (move) and resource (mouse position), with a specific verb. Among sibling tools like browser_mouse_click_xy and browser_mouse_drag_xy, this tool uniquely focuses on moving without clicking or dragging.

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 vs alternatives such as browser_hover, browser_mouse_click_xy, or browser_drag. The description does not clarify scenarios where a plain move is preferred (e.g., to position the cursor before a separate click) vs other mouse actions.

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