Mouse drag

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation uses the left button and follows a press-move-release sequence, but it omits coordinate space, timing, side effects, error behavior, and return semantics.

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 tightly structured sentence with zero wasted words. It is front-loaded with the action and immediately explains the role of all four coordinates.

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 pointer-automation tool, the core action and parameter roles are covered. However, with no annotations and no output schema, the description should also mention coordinate system, whether the drag is synchronous, and any meaningful side effects or return 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 0%, so the description must compensate for the four undocumented numeric parameters. It does this well by mapping (x1,y1) to the press point and (x2,y2) to the release point, though it does not specify coordinate origin or units.

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 precise mouse operation: press the left button at one point, move to another, and release. This clearly identifies a drag action and distinguishes it mechanically from click or move_mouse, though it does not explicitly name those alternatives.

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 explains how the drag is performed but gives no guidance on when to use it instead of click, move_mouse, scroll, or other sibling tools. There are no stated preconditions, exclusions, or alternative-selection rules.

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