swipe

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

No annotations are supplied, so the description carries the full disclosure burden. It explains the hold_ms press-then-drag behaviour, but says nothing about duration, timing/wait semantics, or that this performs a real input action on the device with side effects.

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?

A single tight sentence with the core action front-loaded and no filler. The trailing 'i.e. drag' is slightly redundant given the hold_ms explanation but costs little.

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?

An output schema exists so return values need not be described, but for a 6-parameter gesture tool with no annotations and zero schema coverage, half the parameters (duration, wait, observe) and the side-effect profile are left unexplained.

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% across 6 parameters, and the description only adds meaning for start, end (accepted formats) and hold_ms. duration_ms, max_wait_ms and observe_after remain undocumented anywhere, so compensation is only partial.

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?

States a specific verb and resource: 'Swipe from `start` to `end`', with the coordinate format clarified. It is clearly distinguishable from tap, long_press and pinch, though it does not explicitly contrast with the sibling 'scroll'.

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?

Usage is implied rather than stated; the note that 'hold_ms > 0' turns the swipe into a drag gives one concrete condition for choosing behaviour. There is no explicit guidance on when to prefer scroll, pinch or long_press instead.

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