swipe

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the tool returns verification evidence (executed, screen_changed, changed_elements, screen_hash), which implies the gesture is a state-changing input. However, it does not mention potential side effects like triggering animations, whether the swipe is a fling or drag, or if any permissions are needed.

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 extremely concise at two sentences, with the core action front-loaded. Every sentence adds value (action and return structure), with no redundant 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 tool is relatively simple, and the description covers the action and return values. However, it lacks guidance on selecting this tool over similar siblings (e.g., scroll_page vs. swipe) and does not explain the practical differences between 'short' and 'long' distances beyond the schema. Given the output schema exists, the return value description is supplementary, but the missing usage context with siblings is a notable gap.

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 input schema fully describes all three parameters (device, distance, direction) with coverage at 100%. The description adds little beyond the schema, only restating direction options. Since the schema already provides parameter-level explanations, the baseline score of 3 is appropriate.

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's action ('Swipe the screen') and the supported directions, distinguishing it from sibling tools like tap or scroll_page. The verb-resource pair is specific and unambiguous.

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 offers no guidance on when to use swipe versus alternatives (e.g., scroll_page, tap) or any prerequisites like device connection. It only states what the tool does, not the appropriate context for invoking it over siblings.

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