Swipe-Tool

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the fixed duration ('over 300ms') and describes the effect on scrolling direction. It does not mention coordinate system, edge cases, or potential side effects, but for a simple gesture tool this is reasonably transparent.

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 only two sentences, with no wasted words. The primary action and coordinates are stated first, followed by practical scroll-direction tips. This is exceptionally concise and well-structured for agent consumption.

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 tool with four required parameters and no output schema, the description covers the core action, duration, and scroll semantics. The main omission is the coordinate system context (e.g., screen pixels, relative vs absolute), which could affect correct invocation. Overall it is nearly complete but not fully self-contained.

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 bare integer fields. It does give meaning to x1,y1,x2,y2 as start and end points, and explains the relationship between y-coordinates and scroll direction. However, it omits essential semantics like coordinate units, origin, and valid ranges, leaving the agent with incomplete information for constructing correct values.

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 a specific action ('Swipe from (x1,y1) to (x2,y2)') on a resource identified by coordinates. It conveys that this is a gesture tool and provides direction semantics for scrolling. However, it does not explicitly distinguish itself from the sibling Drag-Tool, so there is some ambiguity about when to prefer Swipe over Drag.

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 practical usage guidance for scrolling: 'To scroll DOWN, swipe from bottom to top. To scroll UP, swipe from top to bottom.' This clearly instructs the agent on how to achieve a specific scroll direction. It does not, however, discuss exclusions or alternatives such as Drag-Tool, leaving some when-to-use context implicit.

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