Swipe

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

No annotations exist, so the description must disclose behavior itself. It adds the legacy-seconds detail about duration, but does not explain coordinate system, swipe speed/timing defaults, or side effects of swiping on the device. For an input action that can affect UI state, this is a real gap.

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?

The text is compact and front-loaded: the action and coordinates come first, with a short clarifying note after. It earns its place with no filler, though it is terse enough that some content is missing.

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 simple two-point swipe with an output schema, the core call is understandable: coords are required and duration semantics are hinted. Missing details (duration_ms default behavior, device selection, when to choose swipe vs scroll) leave moderate ambiguity for an agent without prior context.

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%, so the description must compensate; it only clarifies duration's unit/legacy status. The four coordinates are self-explanatory by naming, but device and duration_ms/'duration vs duration_ms' semantics remain undocumented.

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 names the action ('Swipe') with explicit coordinates, so the tool's purpose is unambiguous and distinguishable from tap/scroll siblings. It could mention the target surface (screen) or that it is a touch gesture, but the intent is clear.

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 use a swipe over the many sibling gestures (tap, long_press, scroll_*), nor when device, duration_ms, or duration should be provided. The only usage hint is that duration is for old clients, which is a compatibility note, not a selection criterion.

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