mouse_drag

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

With no annotations, the description carries the full burden. It discloses that it is a left-button HID-level drag and uses screen points, which is useful. However, it does not mention details like coordinate origin, drag speed, whether the button is released at the end, or any side effects beyond the drag itself.

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?

A single sentence that conveys the essential action and parameters with no wasted words. It is front-loaded and immediately understandable.

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 4-parameter input tool with no output schema and no annotations, the description is mostly complete: it states the action, the input points, and that coordinates are screen points. It lacks guidance on alternative tools, but the core functionality is well-covered.

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. The phrase 'from (fromX, fromY) to (toX, toY)' clearly maps the four parameters to endpoints, but it does not define the coordinate system origin or units beyond 'screen points'. Parameter names are self-explanatory, but deeper semantics are missing.

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 ('drag') and identifies the exact resource and action: a left-button HID drag from one coordinate to another. It clearly distinguishes from sibling tools like mouse_move or click by specifying the left-button press-and-move behavior.

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 it (whenever a drag action is needed) but does not explicitly state when not to use it or compare it to alternatives like mouse_move or click. It provides no exclusionary guidance.

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