swipe

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'quick coordinate fling' without explaining whether this simulates a touch gesture, has side effects on the device, requires a connected device, or what response to expect. The lack of behavioral detail is a significant gap for a tool that performs an interaction.

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 a single, front-loaded sentence with no filler. It is concise and to the point, though it could be slightly more informative. No redundant information is present, so it earns high marks for efficiency.

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 the tool's complexity (29 parameters, no output schema, no annotations), the description is far too sparse. It does not explain the gesture behavior, the meaning of the return value, device requirements, or how the repeat pattern works. The schema covers parameter details, but the overall context of the tool is under-specified.

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 97%, so the baseline is 3. The description's 'coordinate' and 'repeat pattern' align with the from/to and count/pattern parameters, but these are already well-described in the schema. The tool description adds minimal semantic value beyond what the schema already provides.

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 action ('coordinate fling') and mentions optional repeat patterns, which conveys a swipe gesture with start/end points. It distinguishes from sibling tools like click or longpress, though 'fling' is slightly informal and could be clearer. Overall, it is specific enough to identify the tool's primary function.

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?

No guidance is provided on when to use this tool versus alternatives like scroll, gesture, or press. The description gives no context about use cases, prerequisites, or scenarios where swipe is preferred. There is no mention of when not to use it.

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