adb_swipe

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

No annotations are provided, so the description carries full behavioral disclosure burden. It states the core behavior (swipe over duration) but doesn't mention that duration defaults to 300ms, whether the gesture is synchronous/precise, or any side effects on the device. For an input tool, it provides minimal behavioral detail.

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?

Single sentence, efficiently communicates the core purpose. No wasted words. However, given the low param coverage, extra sentences clarifying coordinate semantics and duration default would have been beneficial without harming 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?

Simple tool, but with 5 undocumented parameters, no output schema, and no annotations, the description leaves significant gaps. It doesn't explain the coordinate system origin, the effect of duration_ms default (300ms), or behavior when coordinates are out of screen bounds. The description is adequate for identifying the tool but insufficient for correct parameter handling.

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 only 17% (1 of 6 params documented). The description explains what x1,y1,x2,y2 mean collectively but doesn't clarify the origin/coordinate system (e.g., screen pixels, top-left origin), or that duration_ms has a default. The serial param is documented in schema but its structure (host:port format) is only partially conveyed.

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 uses a specific verb (swipe/drag) with clear coordinates (x1,y1 to x2,y2) and a duration parameter. It clearly distinguishes from sibling tools like adb_tap or adb_key by describing gesture semantics. It could state the screen dimension context but is clear enough about its function.

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?

No guidance on when to use swipe vs tap vs text. No context about use cases like scrolling, dismissing dialogs, or gesture navigation. It doesn't mention when this is appropriate versus alternative input methods.

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