mouse_move

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

Annotations already provide destructiveHint=true, but description adds no further behavioral context such as potential side effects (e.g., triggering hover events, focus changes). Description fails to add value beyond 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?

Single sentence with clear, front-loaded action. No extraneous words. Efficient for agent parsing.

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 absence of output schema and presence of many mouse-related sibling tools, the description is too sparse. It lacks context on return behavior, coordinate system, or how this interacts with other mouse actions.

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 has 0% description coverage for parameters, so description must compensate. It only states that x,y are absolute screen coordinates, but does not specify coordinate system, units (pixels?), range, or that they are numbers. This is minimally helpful.

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?

Description specifies verb 'Move', resource 'mouse pointer', and context 'absolute screen coordinates (x, y)'. This clearly distinguishes it from sibling tools like mouse_drag or mouse_scroll that involve relative moves or drag actions.

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 such as mouse_drag or mouse_scroll. The description does not mention prerequisites, caveats, or when this tool is appropriate over others. The agent is left to infer usage context.

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