classic_mac_mouse_move

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

No annotations are provided. The description does not disclose important behavioral details such as whether coordinates are absolute or relative, what happens with out-of-bounds coordinates, or if mouse events are generated. It only states 'without clicking'.

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 that directly communicates the tool's purpose. It is concise and front-loaded, with no superfluous information. However, it could benefit from slightly more detail without becoming verbose.

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 no output schema and no annotations, the description is incomplete. It fails to specify coordinate units, screen vs. window coordinates, or behavior with multiple displays. For a mouse movement tool, these details are important for correct invocation.

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 coverage is 100% with descriptions for x, y, and target. The description adds no additional meaning to the parameters beyond what the schema already provides, resulting in a baseline score of 3.

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 action ('Move the cursor') and the resource ('to screen coordinates without clicking'). It effectively distinguishes the tool from siblings like classic_mac_click (clicking) and classic_mac_mouse_drag (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?

The description implies it is for moving without clicking, but it does not explicitly state when to use it versus alternatives or clarify when the optional 'target' parameter is needed. No guidelines on coordinate system or prerequisites.

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