swipe

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

The description adds minimal behavioral information beyond the name, such as the 'absolute' coordinate qualifier, but does not disclose side effects, execution behavior, device interaction, or any required permissions. With no annotations to rely on, the description fails to carry the burden of behavioral disclosure.

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 concise sentence with no wasted words, efficiently conveying the basic purpose. It is appropriately short for a simple action, though it could benefit from additional detail without becoming verbose.

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 has 7 parameters and no annotations, the description is far from complete. It omits important details about parameter meanings (steps, duration, device), usage context, and behavioral implications. The existence of an output schema partially reduces the need to explain return values, but the description still leaves significant gaps.

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?

The description clarifies that start_x, start_y, end_x, end_y are absolute screen coordinates, addressing the core coordinate parameters. However, it does not explain the meaning or purpose of 'steps', 'duration', or 'device', leaving the remaining 3 of 7 parameters undocumented in a context where schema descriptions are absent.

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 action (swipe) and the resource (screen coordinates), specifying that it operates between two absolute coordinate points. This is a distinct operation compared to sibling tools like 'touch' or 'keyevent', making it easy to identify when to select this tool.

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?

There is no guidance on when to use this tool versus alternatives, such as 'touch' for a single tap or other gesture tools. The description only defines the action without contextualizing its use cases or prerequisites.

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