swipe

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

No annotations are provided, so the description carries the burden. It adds contextual behavior by indicating the gesture is used for scrolling and notifications, but does not disclose other behavioral aspects such as speed, sensitivity, edge cases, or return values. For a simple swipe gesture this is adequate but not rich.

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 sentences plus two example lines. It is front-loaded with the core action and immediately gives practical usage patterns. Every sentence 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?

For a simple gesture tool with an output schema, the description covers the primary usage and provides actionable examples. It misses documentation of duration_ms and any error/edge-case behavior, but the tool's simplicity and existing examples make the description reasonably complete. The output schema likely covers return values, so the description need not explain those.

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 coverage is 0% and the schema has no descriptions, so the description must compensate. It provides concrete examples showing how x1, y1, x2, y2 map to start/end points (e.g., scroll down vs up), giving meaning beyond the raw schema. However, it does not explain the duration_ms parameter or define the coordinate system/units, leaving some parameters under-specified.

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 tool performs a swipe gesture from (x1,y1) to (x2,y2), which is a specific verb+resource combination. It distinguishes itself from siblings like tap or long_press by specifying the swipe action and coordinates. The examples further clarify intent.

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 explicitly says 'Use for scrolling, pulling down notifications, etc.' and provides common patterns for scroll up/down, giving the agent clear guidance on when to invoke this tool. It does not explicitly mention when not to use it or provide alternative tool names, but the guidance is sufficient for the intended use cases.

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