mouse_drag

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the press-drag-release sequence and the coordinate system origin (top-left of main display). It does not mention potential side effects, button behavior during drag, or consequences of invalid paths, leaving some behavioral aspects opaque.

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 exceptionally concise: two sentences. The first sentence states the action and the second provides coordinate computation context. There is no redundant information or filler.

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?

Given no output schema, the description does not need to specify return values. It covers the core operation and coordinate system, but leaves optional parameter behaviors (button, duration, fresh screenshot requirement) unexplained. For a tool of moderate complexity, this is a notable gap.

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?

The description adds meaningful semantics for the 'path' parameter, explaining that coordinates are logical points and how to compute them from screenshot metadata. However, it provides no explanation for 'button', 'duration_ms', or 'require_fresh_screenshot', which is notable given the schema description coverage is 0%.

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 explicitly states the action: 'Press, drag along path, release.' This clearly indicates a mouse drag operation, distinguishing it from sibling tools like mouse_move (which moves without pressing) and mouse_click (which clicks at a point). The mention of coordinate computation from screenshot metadata further defines the tool's scope.

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 usage for drag gestures but does not explicitly contrast it with alternatives or state when not to use it. However, it does provide a critical usage tip: coordinates are logical points derived from the screenshot tool's bounds_pt and px_per_pt metadata, which aids correct invocation.

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