Swipe

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

With no annotations, the description carries the full burden. It reveals that shorter durations result in faster swipes and longer in slower drags, which is helpful. However, it does not mention whether the swipe is instantaneous or if there are any side effects (e.g., triggering scroll inertia). It also does not specify coordinate system origin or bounds.

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, each adding value: first states action and coordinates, second lists use cases and explains duration effect. No filler or repetition.

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 the tool's simplicity (swipe gesture) and that input schema covers all parameters with descriptions, the description is quite complete. It covers purpose, usage scenarios, and behavioral nuance of duration. A small gap is the lack of coordinate origin clarification, but overall it is sufficient for an agent to use correctly.

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 100%, and each parameter has a clear description in the schema. The description adds a note about duration affecting speed, which is already implied by the default and schema description but adds context. However, it does not elaborate on coordinate expectations (e.g., origin at top-left) or provide typical values beyond duration.

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 between two coordinates. It lists common use cases (scrolling, dismissing notifications, navigating pages, pulling down notification shade), but does not explicitly distinguish it from sibling tools like scroll or drag. However, other sibling names (tap, long_press, double_tap) are distinct enough, so purpose is clear.

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 states when to use the tool: 'to scroll through lists, dismiss notifications, navigate between pages, or pull down the notification shade.' It also explains the effect of the duration parameter (flick vs drag). However, it does not mention when not to use it or alternatives among sibling tools.

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