cdp_mouse_move

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

No annotations are provided, so the description carries full responsibility. It only states the basic action and that no click occurs, but provides no details about coordinate system, whether events are fired, browser prerequisites, or handling of invalid coordinates. This is a significant gap for a user-action simulation tool.

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 one short sentence that directly conveys the purpose. It is front-loaded with the action ('Move the mouse') and wraps up the key constraint ('without clicking'). No wasted words.

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 action, the description is adequate yet leaves out important details such as coordinate reference system, behavior on invalid coordinates, and whether a page must be loaded. Since there is no output schema, the description should have provided at least minimal context about expected behavior.

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 only 33% (only session_id has a description). The description adds the term 'page coordinates' to clarify x and y, but does not explain units, origin, or whether coordinates are relative to viewport or page. This partial compensation is helpful but not fully sufficient.

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 mouse to page coordinates without clicking. It uses a specific verb (move) and resource (mouse), and the phrase 'without clicking' distinguishes it from sibling tools like cdp_click and cdp_hover.

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 when to use the tool (when you want to move the mouse without triggering a click) but does not explicitly name alternatives or exclusions. Siblings like cdp_click and cdp_hover are not mentioned, so the guidance is mostly implicit.

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