mouse_move

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

Description discloses cursor movement to absolute coordinates and optional animation, but omits instant jump and focus disruption confirmation. Annotations provide idempotentHint and destructiveHint, so no contradiction.

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 concise with clear sections for Args and Returns. It could be slightly more efficient, but overall well-structured.

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 tool's complexity (nested object with 5 properties) and annotations, the description covers the basics but misses important parameters like instant and confirm_focus_disruption, and does not explain the return format beyond 'JSON with the resulting cursor position'.

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 description mentions x, y, and duration, but does not cover instant or confirm_focus_disruption. Since the schema already has detailed parameter descriptions, the description adds marginal value beyond the schema.

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 'Move the mouse cursor to an absolute screen coordinate,' specifying the verb and resource. It implicitly distinguishes from sibling tools like mouse_click or mouse_drag, but does not explicitly differentiate.

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 on when to use this tool versus alternatives. The description does not mention contexts where mouse_move is preferred over other cursor movement tools or when not to use it.

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