Swipe between two coordinates

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

Annotations already indicate non-read-only, non-destructive, non-idempotent, and open-world. The description adds behavioral context by naming the underlying command (adb shell input swipe), default duration, and typical effects (scroll, dismiss, gesture). No contradictions.

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?

Two sentences, no unnecessary words. Action and parameters in first sentence, use cases in second. Excellent conciseness.

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 gesture tool with 6 parameters and no output schema, the description covers purpose, parameters, and usage context. Missing details like coordinate limits or response behavior, but adequate for most agents.

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 low (33%) with only serial and durationMs described. The description explains the overall meaning of coordinates and duration but does not detail each parameter's bounds or coordinate system. It adds value but could be more precise.

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 sends a swipe gesture using adb shell input swipe, specifies coordinates and duration, and gives example use cases (scrolling, dismissing overlays). It distinguishes from sibling input tools (tap, text, key) by the action type.

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 includes explicit use cases ('useful for scrolling lists, dismissing overlays, performing simple gestures'), providing context for when to use. It does not explicitly mention alternatives or when not to use, but the examples are sufficient for typical scenarios.

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