swipe

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

With no annotations, the description carries the full burden. It discloses one genuine behavioral trait (slow swipes register as drags), which is valuable, but says nothing about the verification side effect (verify=true default), the coordinate space, or whether the gesture is a mutation with side effects.

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 tight sentences, front-loaded with the core action and followed by the actionable duration heuristic. Every sentence earns its place with no filler.

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 an 8-parameter gesture tool with no annotations and no output schema, the description covers the core motion and one tuning heuristic but omits explanation of the verify/verify_poll_ms/verify_timeout_ms side-effect machinery and coordinate expectations, leaving meaningful behavioral gaps.

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 50% (duration_ms and the three verify params have descriptions; the four coordinate params do not). The description adds a meaningful threshold for duration_ms (>400ms = drag) but offers nothing for the coordinates or the verify/poll/timeout behavior, which is the real gap for an 8-param tool.

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 states a specific verb+resource ('swipes/drags from one point to another') with clear scope, and the parenthetical 'or drags' clarifies the gesture family. It implicitly distinguishes itself from tap/long_press siblings by naming the two-point motion, though it does not name a sibling 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 note 'a slow swipe (>400ms) reads as a drag' gives useful context for choosing a duration, but there is no explicit when-to-use guidance relative to alternatives like tap, long_press, or tap_element, and no prerequisites are stated.

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