drag

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

With no annotations, the description carries full behavioral burden. It discloses the left mouse button and that coordinates refer to the last screenshot, but omits side effects, reversibility, required permissions, and the meaning of the duration and screenshot_after parameters.

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 single sentence is front-loaded with the core action and coordinate reference, with no wasted words. It is appropriately sized for a simple pointer operation.

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 6-parameter action tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It does not explain optional parameters, coordinate semantics, side effects, or when to use drag over other interaction tools.

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 names the four required coordinate parameters in sequence but does not explain their units, reference frame, or semantics, and it completely omits the duration and screenshot_after optional parameters.

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 verb ('Drag') and resource (mouse left button from (x1,y1) to (x2,y2) in the last screenshot). It is distinguishable from siblings like click and double_click, though it does not explicitly name an alternative or clarify when a drag is preferred over other interactions.

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?

No guidance is given on when to use this tool versus alternatives like click, scroll, or set_field. The phrase 'in the last screenshot' implies a prerequisite but does not explain the context or conditions for choosing a drag operation.

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