Drag

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the drag uses the left mouse button and implies a press-move-release gesture, but it does not describe timing, button-release behavior, side effects, permissions, or what happens on failure.

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 definition is a single front-loaded sentence with no wasted words. The core action and coordinate endpoints appear immediately.

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 7-parameter interaction tool with no annotations and no output schema, the description is too sparse. It omits the optional image/screen/look_after parameters and does not explain the drag lifecycle or result 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?

The description gives meaning to the four required coordinate parameters by identifying them as start and end points. However, with only 43% schema description coverage, the optional parameters image, screen, and look_after are not explained in the description, and the coordinate system/units are left ambiguous.

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 action and resource: a left-button drag from (x1,y1) to (x2,y2). It also lists representative outcomes such as moving files and selecting text. However, it does not explicitly distinguish itself from the sibling browser_drag or click tools.

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 examples 'move files, select text, resize, reorder' imply when the tool is useful, but there is no explicit guidance on when to choose drag over click, browser_drag, or other pointer tools. No exclusions or prerequisites are stated.

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