ios_swipe

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

No annotations, so the description carries the full burden — and it discloses two non-obvious traits: direction follows the finger ("up" scrolls content down) and duration controls fling speed. It omits what happens if neither direction nor points are supplied, and says nothing about prerequisites such as a booted simulator or foregrounded app.

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?

Front-loaded with the two operating modes before the Args block, and the counterintuitive direction semantics are called out early. The Args block is tight and every line adds meaning; nothing is padded.

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?

For a 7-parameter, zero-annotation, no-output-schema gesture tool, the description covers all parameters, both invocation modes, and the main gotcha. It stops short of describing device resolution behavior when device is null and of any failure semantics, which an agent would want before firing a gesture.

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 coverage is 0%, so the description must compensate, and it mostly does: it enumerates the four direction values, gives units (points) for all four coordinates, flags that point mode is used 'instead of direction', and explains duration semantically. It still doesn't state that the two modes are mutually exclusive by rule, nor mention the 0.3s default or what happens when nothing is passed.

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?

Opens with a specific verb+resource ('Swipe') and immediately splits it into its two modes: a named direction from screen center, or explicit from/to points. That immediately separates it from ios_tap and ios_press, which take single points, though it never names those siblings explicitly.

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?

Provides one concrete recipe ('to go back in most apps, swipe from x=2 to x=250 at mid-height'), which is genuine usage guidance. However, it never states when to choose swipe over ios_tap or ios_press, or when a gesture is inappropriate. Usage is implied rather than stated.

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