swipe

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

With no annotations present, the description carries the behavioral disclosure burden. It adds useful facts: the action is quick, can repeat, and times out after 90s. However, it does not describe what happens on completion, whether the gesture mutates UI state, or how the repeat pattern behaves if interrupted.

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 short sentences with no filler. The core action is front-loaded, and the key behavioral constraint (90s timeout) is included without redundantly repeating schema details.

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?

Despite a rich schema, there are no annotations, no output schema, and many overlapping sibling tools. The description is too thin to fully guide an agent on tool selection and invocation, especially regarding when to use swipe over alternative gesture commands and what response to expect.

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 95%, so the schema already documents nearly all parameters. The description adds 'optional repeat pattern' and the concept of a quick fling, but does not meaningfully expand on from/to semantics or the pattern enum beyond what the schema 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') over a clear resource, and the required from/to coordinates in the schema make the operation concrete. It is distinct enough from click, longpress, and scroll, though it does not explicitly name siblings to disambiguate.

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 swipe versus related tools like gesture, scroll, or longpress. There is no context about UI state, prerequisites, or when a coordinate-based fling is preferred over an element-based interaction.

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