Swipe

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

With annotations already indicating readOnlyHint=false and destructiveHint=false, the description adds no further behavioral context. It does not explain side effects, coordinate system, duration implications, or whether the gesture blocks until completion.

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 sentence that is immediately front-loaded with the verb 'Swipe'. It is concise with no wasted words, earning its place by stating the core action clearly.

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 tool with 6 parameters, no output schema, and minimal annotations, the description is inadequate. It leaves critical details about coordinate reference, duration semantics, and device targeting unspecified, making the tool difficult to use correctly without additional information.

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%, and the description only hints at coordinates (x1, y1, x2, y2) via 'from one coordinate to another'. It provides no meaning for the 'serial' or 'duration' parameters, nor does it clarify the expected units or coordinate space.

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 'Swipe on screen from one coordinate to another' clearly states the action (swipe), the target (screen), and the specific nature (from one coordinate to another), which distinguishes it from sibling tools like tap and longPress that involve a single point or hold.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention appropriate scenarios (e.g., scrolling, swiping between pages) or exclusions, leaving the agent to infer usage solely from the tool name.

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