Swipe Screen

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

The description does not mention its destructive nature (annotations indicate destructiveHint: true), nor any behavioral details like system gestures (e.g., edge swipes), duration, or acceleration. The annotations partially cover safety, but the description adds no behavioral context beyond the bare action.

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 consists of a single short sentence, which is concise but overly sparse. It sacrifices useful detail for brevity, making it insufficient for an agent to fully understand the tool's behavior.

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 destructive hint, a more informative description is warranted to explain potential consequences (e.g., triggering system gestures, causing navigation). There is no output schema, so the description should clarify return values or side effects. The current text is inadequate.

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 has 100% description coverage, so the schema already documents each parameter well (e.g., device, direction, optional x/y/distance). The description adds no extra meaning; it is merely a short phrase that repeats the tool name.

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 'Swipe on the screen' is a near-tautology of the tool name and title, providing minimal insight. It does not specify the effect (e.g., scrolling, navigation) or distinguish from sibling tools like mobile_click_on_screen_at_coordinates or mobile_long_press_on_screen_at_coordinates.

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 this tool versus alternatives. For example, it does not explain that swiping is for scrolling or gestures, while clicking or tapping is for selecting elements. The presence of many sibling tools makes this omission significant.

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