swipe

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

No annotations exist, so the description carries the full disclosure burden. It contributes one genuinely useful fact — that coordinates are in screenshot pixels, giving a reference frame — but says nothing about speed/duration behavior, whether the call blocks until the gesture completes, device-connection requirements, or what happens if coordinates fall outside the screen.

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?

A single front-loaded sentence with no filler — the coordinate semantics arrive immediately. The terseness is efficient, though it borders on under-specification rather than wasteful verbosity.

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 five-parameter device-control tool with no annotations, no schema descriptions, and no output schema, the definition is too thin. An agent can form the gesture but lacks the surrounding operational facts (units relative to device density, duration effect, preconditions) needed to invoke it confidently.

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%, and the schema labels are bare ("X1", "Y1", etc.). The description clarifies that the four coordinates are screenshot-pixel points, which is real added meaning, but it never mentions duration_ms or its default of 300 or how duration affects gesture interpretation.

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 (swipe) plus the exact endpoints it interpolates between, so the action is unambiguous. It does not differentiate itself from sibling gestures such as scroll, long_press, or wake_and_unlock_swipe, which leaves the agent to infer the boundary.

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 prefer this over scroll (which likely does a canned directional swipe) or wake_and_unlock_swipe, nor any precondition such as requiring a selected device or a fresh screenshot. The agent must guess from tool names alone.

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