Move the mouse

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

The description adds meaningful behavioral context beyond the annotations by naming the underlying tool (cliclick) and stating required permission settings. It does not elaborate on failure behavior or side effects, but the prerequisite disclosure is valuable given the annotations only cover read-only/destructive hints.

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?

Two short sentences: the first states the purpose, the second states prerequisites. There is no filler, and the most important information is front-loaded.

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?

For a simple two-parameter move action with no output schema, the description covers purpose and prerequisites sufficiently. Minor gaps such as coordinate origin and failure behavior are not critical because sibling 'get_screen_size' provides coordinate context and the action is straightforward.

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 both x and y described as coordinates in screen points. The tool description adds no extra parameter meaning, so the baseline of 3 applies since the schema already does the heavy lifting.

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 uses a specific verb and resource: 'Move the cursor to screen coordinates.' This clearly states the action and distinguishes it from click/drag/scroll by naming the outcome, though it doesn't explicitly reference sibling tools to differentiate them.

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 provides concrete prerequisite conditions ('Requires admin mode AND MACCTL_ALLOW_INPUT=true (cliclick)'), which is useful context. However, it does not explain when to choose this tool over siblings like click or drag, leaving the selection to inference.

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