android_swipe

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

Annotations already flag the tool as not read-only, destructive, and non-idempotent, so the description is not burdened with safety disclosure. It adds the behavioral detail that the gesture is expressed in raw screen coordinates, but it does not mention possible effects such as navigation, dismissal, or destructive actions.

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?

One short sentence with no filler, and the core action is front-loaded. It is efficient but so terse that it omits useful qualifiers; still, this is conciseness rather than bloat.

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?

With five parameters, no output schema, and no parameter descriptions, a four-word description is insufficient. The agent is left without usage guidance, duration semantics, coordinate-system details, or disambiguation from android_scroll.

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 must carry parameter meaning. 'Screen coordinates' clarifies that x1/y1/x2/y2 are raw screen positions, but it does not explain durationMs, units, coordinate origin, or that the swipe goes from (x1,y1) to (x2,y2).

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 names a specific verb (Swipe) and resource (screen coordinates), making it clear this is a coordinate-based gesture tool. It is distinguishable from taps and long-presses, though it does not explicitly differentiate itself from the sibling android_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?

No guidance is provided about when to use this tool rather than android_scroll, android_ui_click, or other gesture tools. The one-line description leaves the selection decision entirely to the agent.

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