adb_swipe

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

No annotations provided; description does not mention any behavioral aspects such as duration, coordinate system, or that this is a touch simulation. The agent gets no insight into side effects or operation constraints.

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?

Extremely concise (one sentence) but at the expense of necessary detail. The description is under-specified, missing essential context that a single sentence cannot adequately convey for a 6-parameter tool.

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 6 parameters, no output schema, and no annotations, the description is wholly inadequate. It fails to explain coordinate space, behavior of duration, or return value, leaving the agent with almost no actionable information.

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?

With 0% schema description coverage and 6 parameters (including required fields like serial, x1, y1, x2, y2), the description adds no meaning beyond the parameter names. The agent has no clue about coordinate ranges, units, or the purpose of 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 'Simulate a swipe gesture' clearly identifies the action as a gesture type, but lacks detail such as coordinate start/end points or that it's a touch simulation. It distinguishes from tap but not precisely among siblings like adb_tap or adb_input_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?

No guidance on when to use swipe versus alternative gestures (tap, press key, etc.). No context about prerequisites or expected outcomes, leaving the agent to infer usage from the name alone.

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