mouse_move

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

With no annotations, the description carries the behavioral burden and does well by explaining that the tool only moves without clicking, that desktop mode uses global screen pixels, and that browser mode uses viewport pixels while syncing the real OS pointer on visible browsers. It omits details such as hover-event side effects, permissions, and duration behavior.

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 compact and front-loaded: purpose first, then mode-specific coordinate behavior, then the alternative tool recommendation. Every sentence adds useful information without repetition.

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?

An output schema exists, so return values do not need description coverage. The main gaps are the undocumented duration parameter and the absence of side-effect or error-condition details, but the core behavior and usage routing are otherwise complete.

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 description coverage is 0%, so the description must compensate. It clarifies the coordinate semantics for x and y in both modes and explains the mode enum, but it does not explain the duration parameter at all, leaving part of the four-parameter surface undocumented.

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 states a specific action and resource: moving the mouse pointer without clicking. It distinguishes the two modes and names the sibling tool smart_move as the alternative for target-description-based movement.

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?

It explicitly says to prefer smart_move when only a target description is known, and it gives clear guidance for choosing desktop versus browser mode based on the coordinate system and visible browser syncing. This is enough to route an agent between moving by known coordinates and moving by description.

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