swipe

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

With no annotations provided, the description carries the full burden. It discloses the coordinate system, alias parameters, and swipe duration effect. However, it does not mention what happens on failure, out-of-bounds coordinates, or whether the tool provides any return value or feedback.

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?

Three sentences that are well-structured: the first states the core action, the second details parameters and aliases, and the third gives key usage advice. Every sentence adds value with no redundancy or filler.

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?

The description covers the core functionality, parameter meanings, and usage hints. Given the tool has 8 parameters and no output schema, it adequately prepares an agent for basic use. However, it lacks information about return behavior, error handling, or preconditions (e.g., device connectivity), which reduces completeness.

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 coverage is 100%, but the description adds value beyond the schema by explaining the alias convention (x,y for x1,y1) and providing practical context for scrolling direction and duration behavior. This helps the agent understand parameter semantics more intuitively.

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 clearly states the tool performs a swipe/drag gesture from a start to an end point using device pixels. However, it does not differentiate from the sibling 'drag' tool, which may have similar functionality.

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 specific usage guidance for scrolling (high y to low y for scroll down) and explains the effect of duration on speed. However, it lacks explicit comparisons to alternatives like 'drag' or 'tap', and does not state when not to use this tool.

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