swipe

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

The description discloses the return evidence structure ({executed, screen_changed, changed_elements[], screen_hash}), which adds useful behavioral context. However, with no annotations, it does not cover side effects, failure conditions, or device requirements.

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 two concise sentences with no wasted words. It front-loads the action and immediately specifies the return evidence, making it easy to parse.

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 simple swipe tool, the description is largely complete: it mentions the return output and the schema covers most parameters. However, it does not differentiate from overlapping siblings like scroll_page or smart_scroll, and session_id remains undocumented, leaving some 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?

Schema coverage is 75% (direction, distance, and device have descriptions; session_id does not). The description adds no parameter-level detail beyond what the schema already provides, so it does not compensate for the missing session_id semantics.

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 the screen') and the specific scope (direction: up/down/left/right). This distinguishes it from siblings like tap or scroll_page.

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 over alternatives like scroll_page or smart_scroll. The description only states what it does, not the appropriate context or exclusions.

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