swipe

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

With no annotations, the description carries the full burden of explaining behavior, but it only states that a swipe occurs. It does not disclose coordinate system, screen origin, touch-injection semantics, whether this produces a fling or a drag, side effects, or possible output behavior.

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 a single concise sentence and front-loads the key behavior. However, for a tool with six parameters and no annotations, the brevity veers into under-specification rather than efficient completeness.

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?

The tool is a gesture action with no annotations and only minimal description. It omits important operational context such as coordinate space, optional serial semantics, and interaction with the UI. An output schema exists, so return values may be covered elsewhere, but the behavioral context is insufficient for confident 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. It does add meaning by identifying x1,y1 and x2,y2 as endpoints and duration_ms as the gesture duration. However, it leaves serial unexplained and does not clarify coordinate units or whether coordinates are absolute or relative.

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 the action (a swipe gesture) and specifies its core inputs: start point (x1,y1), end point (x2,y2), and duration_ms. This distinguishes it from simple taps or presses, though it does not clearly differentiate it from similar sibling tools like drag or 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?

The description provides no guidance on when to use swipe versus drag, scroll, or other gestures. It does not mention typical use cases, exclusions, or conditions under which an agent should choose an alternative.

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