Swipe

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about whether the gesture blocks until complete, how duration is interpreted, whether a device must be selected first, or what the return payload contains. For an input-simulating mutation against a UI, this leaves key behavior undisclosed.

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?

Two short sentences, front-loaded with the core action, and the trailing example earns its place by demonstrating real argument values. No 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?

An output schema exists, so return values need not be described. But with zero annotation coverage and 0% schema description coverage, the description omits meaningful gaps: duration units/default behavior and the purpose of the device parameter. For a 6-parameter gesture tool this is thin.

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%, so the description should compensate. It usefully clarifies that coordinates may be fractions or pixels and the example pins the positional order (x1,y1,x2,y2), which covers the four required params. The 'device' and 'duration' parameters are left entirely unexplained, so compensation is only partial.

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?

States a specific verb+resource ('Swipe between two points') with the coordinate space clarified (fractions or pixels). It is distinguishable from the gesture siblings (tap, key, type_text), though it does not explicitly name which alternative to prefer.

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 worked example ('Scroll down = swipe(0.5,0.75,0.5,0.25)') implies a common usage and disambiguates the argument order, which is genuinely helpful. However, there is no explicit when-to-use versus tap/tap_node, and no prerequisites such as needing an active device session.

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