input.swipe

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

With no annotations, the description carries the full behavioral burden. The parenthetical '(generic-layer primitive)' faintly signals that this bypasses UI-semantic layers, but nothing is said about whether the gesture is synchronous, how duration affects fling vs drag behavior, or what happens on a failed swipe.

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?

It is a single front-loaded phrase with zero waste, which is structurally clean. But the extreme brevity here reflects under-specification rather than disciplined conciseness — there is simply not enough content for a 5-parameter gesture tool.

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 tool with 5 undocumented parameters, no annotations, and no output schema, a four-character description is wholly inadequate. An agent cannot determine coordinate conventions, duration semantics, or any behavioral contract from it.

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 0% across 5 parameters, so the description must compensate and largely does not. 'Raw coordinates' implies x1/y1/x2/y2 are screen pixel start/end points, which adds slight meaning beyond the bare 'integer' schema, but duration_ms (default 300) and coordinate units/origin are entirely undocumented.

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 phrase 'raw-coordinate swipe (generic-layer primitive)' names a specific verb+resource and hints at the low-level nature of the operation. However, it offers no differentiation from the many sibling gesture tools such as ui.scroll, ui.click, or input.tap, so an agent cannot tell from the description alone why it would choose this over ui.scroll.

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 when-to-use guidance at all. Nothing tells the agent when a raw-coordinate swipe is preferable to ui.scroll or the higher-level gesture tools, nor whether a device/app context or prior wake-unlock is required.

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