previewapk_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 usefully discloses the duration default (300ms), but says nothing about device targeting (a real concern given sibling tools previewapk_use_device/list_devices), whether the gesture is synchronous, or what happens on failure.

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 compact sentences, front-loaded with the coordinate semantics and the optional/default duration. No filler; every clause carries information the schema lacks.

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 gesture tool with no annotations and no output schema, the description covers coordinate semantics adequately but omits device selection and execution behavior. It is minimally sufficient rather than complete.

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. It does well for five of six parameters by defining x1/y1/x2/y2 as normalized 0..1 fractions and giving duration_ms an optional flag plus default, but the 'device' parameter is left completely undocumented in both schema and description.

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) and resource (screen gesture) with the exact coordinate convention '0..1 fractions', which is the crucial detail for this tool. It is clearly distinct from the tap/press_key/type_text siblings by the gesture name, though it never explicitly differentiates itself from them.

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 statement of when to use a swipe versus alternatives like previewapk_tap or previewapk_tap_text, nor any prerequisite (e.g. an active device). Usage must be inferred entirely from the tool name.

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