swipe

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

Annotations provide readOnlyHint=false and destructiveHint=false, which partially describe the safety profile. The description adds nothing beyond the single gesture statement. It doesn't disclose what happens on a swiped element (scroll vs. navigation), duration semantics, or whether coordinates are absolute screen coordinates. With annotations covering basic safety, the description adds minimal behavioral context.

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?

A single concise sentence that states the core function with zero filler words. It's efficient and front-loaded with the key action. However, for a tool with 6 parameters and multiple gesture siblings, the brevity borders on under-specification.

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?

With an output schema present and 100% schema coverage, the tool relies on structured data for parameters. However, the ambiguous boundary between swipe, drag_drop, and scroll is not addressed, and there's no guidance on coordinate reference frame or device/session prerequisites. For a gesture tool in a broad device-control API, this is incomplete.

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 all 6 parameters (x1,y1,x2,y2,serial,duration) are documented in the schema. The description adds no new parameter information beyond what the schema already conveys. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Perform a swipe gesture from one point to another' clearly states the verb (perform a swipe) and the resource (from one point to another). It distinguishes from siblings like tap, long_press, drag_drop, and scroll reasonably well, though it doesn't sharply differentiate from drag_drop which is a similar gesture-based action.

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?

There is no guidance on when to use swipe vs. alternatives like drag_drop, scroll, or tap. It doesn't mention coordinate system (screen pixels vs. view-relative), prerequisites (device must be on, session active), or inapplicable cases. For a gesture tool with several similar siblings, this is a meaningful gap.

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