swipe

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

With no annotations, the description carries full burden. It discloses key behaviors: duration conversion logic (seconds vs ms), clamping (0.15–2.5s), and resnapshot default. Does not mention destructiveness or side effects, but sufficient for a gesture tool.

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?

Extremely concise; 5 sentences covering purpose, preference, mechanism, clamping, and a use case. No redundant information, front-loaded with clear purpose.

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?

Given 8 parameters and no output schema, the description covers the critical behavioral aspects (duration, resnapshot, use case). Could mention return value or effect on screen, but sufficient for a gesture tool.

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 38% (duration, durationMs, resnapshot have descriptions). The description adds clarity: 'Prefer durationMs (e.g. 280)' and explains the duration handling logic, which goes beyond schema. Other parameters like coordinates are not elaborated, but the main ones are covered.

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 clearly states 'Swipe direction or path', which specifies the verb and resource. It distinguishes itself from sibling tools like tap and double_tap by implying a continuous gesture.

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 guidance on preferring durationMs, handling of duration in seconds vs ms, and a specific use case for resnapshot. However, it lacks explicit comparisons to alternatives like tap or when not to use swipe.

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