mouse_move

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only restates the obvious action and adds the detail that coordinates are screen-based, but it does not mention side effects, limitations, special behaviors (e.g., no click, instant movement), or potential errors. This is minimal and lacks context beyond the primary action.

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 very concise, front-loaded with the main purpose, and structured clearly with a parameter list. Every sentence adds value, and there is no unnecessary text.

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?

The tool is simple, and the combination of a clear purpose plus parameter explanations is sufficient for basic usage. An output schema exists, so return values are covered. However, it could mention coordinate system origin (e.g., top-left) or error behavior for out-of-bounds values, but these are minor omissions.

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?

Although the schema has 0% description coverage, the description includes a parameter section explaining x as horizontal pixel coordinate and y as vertical pixel coordinate. This adds meaningful semantics beyond the bare integer type in 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 the tool's action: 'Move the mouse cursor to the given screen coordinates.' This is a specific verb and resource, and it distinguishes from siblings like mouse_click and get_cursor_position by focusing on movement only.

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 such as mouse_click or get_cursor_position. The description implies it is for positioning the cursor, but it does not state explicit conditions, exclusions, or mention other tools.

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