swipe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the gesture path and duration, but says nothing about coordinate origin, device targeting via serial, required connection state, side effects, or whether the gesture is blocking. For an input action tool with no annotations, this is a significant 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 description is two short sentences and is front-loaded with the core operation. Every sentence earns its place, and there is no filler or repetition.

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?

An output schema exists, so return values do not need explanation. However, with no annotations and 0% schema description coverage, the description is too thin for a six-parameter gesture tool. It omits important context such as coordinate system, serial behavior, and duration units/defaults.

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 for six undocumented parameters. It restates x1, y1, x2, y2, and duration_ms, but adds no coordinate origin, units, or format details. The serial parameter is not mentioned at all, and the duration default is left to the schema.

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 and resource: swipe from one coordinate to another over a duration. It also hints at the primary use case, scrolling/flinging. It is clear, but it does not explicitly distinguish itself from sibling gesture tools such as drag or long_press.

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 second sentence gives clear usage context: 'Use for scrolling/flinging.' This tells the agent when the tool is appropriate. However, it does not state when not to use it or name alternative sibling tools for related gestures.

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