adb_swipe

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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds useful context like swipe duration defaulting to 300ms and device auto-selection, but does not disclose coordinate-space/pixel units, whether the gesture waits for completion, or potential side effects from triggering touch handlers.

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 purpose sentence is followed by a clean argument list with no filler. Every line adds information and the core behavior is front-loaded.

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, the description covers the purpose, every parameter, default behavior, and device selection. Since an output schema exists, return-value explanation is unnecessary; only minor caveats like screen-pixel units are missing.

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%, so the description fully compensates by documenting all six parameters: start coordinates, duration, and optional device serial with auto-selection nuance. This is essential because the input schema only provides names and types only.

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 states a specific action ('Swipe') and resource ('Android device screen') with direction from one point to another. This clearly differentiates it from sibling tools like adb_tap, adb_key, and adb_type_text.

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?

There is no explicit guidance on when to use this tool versus alternatives such as adb_tap, nor mention of prerequisites like a connected Android device. The description only notes auto-selection behavior when a single device is connected, which is parameter context rather than usage routing.

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