Swipe

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

With no annotations provided, the description carries the full burden. It adds one useful behavioral detail: 'Direction swipes are centered on the screen.' However, it omits other critical behavioral traits such as coordinate system, interaction with UI elements, or what observe returns. The disclosure is minimal for a gesture tool.

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 two short sentences that are front-loaded with the action and modes. Every sentence earns its place: the first states the core functionality, and the second adds a practical nuance. There is no filler or redundancy.

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 8 parameters, no annotations, and no output schema, this two-sentence description is insufficient. It does not explain absolute vs relative coordinates, duration semantics, or what the tool returns. The centered-screen detail is helpful, but the overall description leaves significant gaps in operational context.

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 clarifies the mode selection: direction enum for directional swipes and x1/y1/x2/y2 for coordinate-based swipes, which is not fully evident from the schema given only 25% schema description coverage. It also implies mutual exclusivity by saying 'or between two coordinate points.' This adds meaningful context beyond the raw parameter names.

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 identifies the tool's function: performing a swipe gesture either via direction (up/down/left/right) or via coordinate points. This unambiguous verb+resource pairing distinguishes it from sibling gesture tools like tap and long_press.

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 when a swipe gesture is needed, but it does not explicitly state when to choose this tool over alternatives like tap or long_press, nor does it mention exclusions or prerequisites. The mention of two modes (direction vs coordinates) provides some internal guidance, but no external comparison.

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