Swipe Screen

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

The description merely restates the action implied by the title and adds no behavioral context beyond what annotations already provide. Annotations indicate readOnlyHint=false and destructiveHint=false, but the description does not disclose side effects, motion, or platform-specific behavior.

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 with no filler, and the core action is front-loaded. However, it is nearly identical to the title and the available space could have been used more valuably.

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 schema fully documents all five parameters, including defaults and device discovery, so the parameter context is complete. Still, the description lacks behavioral or usage context beyond the action, leaving the agent to infer the effects and appropriate use of the swipe gesture.

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 description coverage is 100%, so the parameters are already well-documented with details like defaults and device discovery. The description itself adds no parameter meaning, but the schema carries the full burden appropriately.

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 states a specific verb ('Swipe') and resource ('the screen'), which clearly distinguishes it from sibling click, tap, and press tools. It is essentially a rephrasing of the title, but the action is 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?

No guidance is provided about when to use a swipe versus alternatives like mobile_click_on_screen_at_coordinates or mobile_long_press_on_screen_at_coordinates. There is no mention of scroll semantics, gestures, or any condition favoring this tool.

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