input_swipe

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the action simulates a swipe, but does not mention prerequisites like screen state or device connection details, potential side effects, failure modes, or what happens when duration is omitted.

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?

The description is compact and front-loaded, stating the action before the parameter details. It is a single sentence with no filler, though the explicit 'Requires x1, y1, x2, y2' listing slightly overlaps with the schema's required fields.

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 that this is a relatively simple swipe gesture tool with five parameters and no output schema, the description covers the essential calling contract: coordinates, duration, and the target device. It could be improved by clarifying coordinate units and duration default behavior, but it is broadly sufficient for correct invocation.

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 compensate by explaining the parameters. It does add meaningful semantics: x1/y1/x2/y2 are labeled as start and end coordinates, and duration_ms is specified as an optional duration in milliseconds. However, it omits details like coordinate units or bounds, and partially repeats schema information.

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 is clear and specific: it simulates a swipe gesture from (x1, y1) to (x2, y2) with optional duration on the Android device. The verb and resource are well defined, though it does not explicitly differentiate itself from sibling input tools like input_tap or input_roll.

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 guidance on when to use this tool versus alternatives such as input_tap or input_roll. The description only explains what the tool does, leaving the agent to infer usage context without exclusions or decision criteria.

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