drag

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds some context by highlighting the slower speed and drag-and-drop purpose, but it does not describe the internal gesture mechanics (press, move, release), coordinate system details, or any return value. This is minimal but not entirely absent.

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 a single, front-loaded sentence that immediately states the action ('Perform a drag gesture') and then adds a concise, valuable parenthetical ('slower than swipe, for drag & drop') that distinguishes it from a sibling. Every word earns its place with no fluff.

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?

The tool has a moderate parameter set (5 params, 4 required) with complete schema descriptions, and no output schema. The description adds the key usage distinction from swipe and clarifies the drag-and-drop purpose. While it doesn't address return values or edge cases, the simplicity of the gesture and strong schema coverage make this reasonably complete.

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 schema already provides descriptions for all five parameters (100% coverage), including starting/ending coordinates and duration with a default. The description does not add additional parameter-level meaning beyond what the schema already states, so the baseline score of 3 applies.

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 clearly states the action: 'Perform a drag gesture from one point to another.' It identifies the resource (gesture) and the specific verb (perform), and it distinguishes this from the sibling tool 'swipe' by adding 'slower than swipe, for drag & drop,' which clarifies its unique purpose.

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 provides useful usage context by noting this is 'slower than swipe, for drag & drop,' implying it should be used for drag-and-drop interactions rather than fast swipes. However, it does not explicitly state when NOT to use it or list alternative tools beyond the implicit contrast with swipe.

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