swipe

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

The description adds minimal behavioral context beyond the annotations. It mentions 'absolute screen coordinates' and 'bounded duration,' but these are somewhat redundant with the schema's min/max values. It does not disclose side effects, error behavior, or device selection implications, which is a gap given the sparse annotations.

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 concise sentence that front-loads the action and includes essential scope ('absolute screen coordinates' and 'bounded duration') without unnecessary 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 description is adequate for a simple gesture tool but lacks details about return values, error conditions, or device prerequisites. Given no output schema and minimal annotations, it could be more complete, but it does cover the core 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?

The description adds meaning by clarifying that coordinates are absolute and that the duration is bounded, which helps interpret the x1/y1/x2/y2 and duration_ms parameters. However, it does not explain the start/end relationship or units, and schema coverage is low, so it only partially compensates.

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 function: swiping between two absolute screen coordinates with a duration. It uses a specific verb ('swipe') and resource ('screen coordinates'), distinguishing it from siblings like tap or type_text.

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 provides no guidance on when to use this tool versus alternatives like tap or type_text, nor does it mention any exclusions or prerequisites. Usage is only implied by the verb itself.

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