swipe_screen

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

With no annotations provided, the description carries the behavior disclosure burden. It explains the gesture pattern and that duration simulates drag, but does not disclose coordinate origin, default duration behavior, or potential side effects.

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 front-loads the core action and avoids filler, making it highly concise and 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 gesture tool with full schema coverage, it is mostly adequate, but it lacks usage guidance relative to sibling gesture tools and does not mention default duration or coordinate system; return behavior is not described but likely irrelevant for this action.

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 covers all 6 parameters (100%), so the baseline applies. The description adds minimal context by relating duration to drag actions, but does not provide meaningful meaning beyond the schema's parameter descriptions.

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?

Description uses the specific verb 'swipe' and resource 'screen', clearly distinguishing it from sibling actions like tap_screen by describing movement between starting and ending coordinates, with an optional duration.

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 phrase 'simulate drag actions' implies a use case for drag gestures, but there is no explicit guidance on when to use swipe versus alternatives like tap_screen or send_keyevent, and no exclusions are mentioned.

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