Swipe

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

With no annotations, the description carries the full behavioral burden. It does disclose the return ("the resulting screen"), which is useful, but says nothing about what side effects the gesture has, what happens if neither coordinates nor direction are supplied, defaults for observe/settleMs, or the device-state impact.

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?

Two short sentences with no filler, and the primary coordinate form is front-loaded ahead of the directional alternative. Efficient, though it could carry more substance for a 10-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?

For a 10-parameter mutation tool with no annotations and no output schema, the description is thin. It omits default behaviors, the zero-required-parameter ambiguity (what happens with no arguments), and how the observation-related parameters interact with the returned screen.

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 only 40%, and the four coordinate parameters plus direction and durationMs are undocumented in the schema. The description partially compensates by clarifying the (x1,y1)→(x2,y2) start-to-end ordering and the direction enum values, but leaves distance, durationMs, observe, settleMs, and includeScreenshot behavior unexplained.

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?

States a specific verb and resource ("Swipe") and enumerates the two supported invocation modes: coordinate pairs and directional finger swipes. An agent can distinguish it from phone_tap or phone_type, though no sibling is named 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?

The description explains the two ways to invoke a swipe but gives no guidance on when to swipe versus tap, key, or back, and no prerequisites or constraints. Usage context is left entirely to inference.

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