swipe

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the action and return type, it doesn't describe important behavioral aspects: what happens if coordinates are out of bounds, whether this interacts with UI elements, what permissions might be needed, or potential side effects. The description is minimal beyond basic functionality.

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 perfectly structured and concise: a clear purpose statement followed by well-organized parameter explanations in a consistent format. Every sentence earns its place, with no wasted words, and the information is front-loaded with the core functionality.

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 tool's moderate complexity (5 parameters, no annotations, but has output schema), the description is partially complete. It covers parameters well and mentions the return type, but lacks context about when to use it, behavioral constraints, and how it relates to sibling tools. The output schema existence reduces the need to explain return values, but more operational context would be helpful.

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 provides excellent parameter semantics that go well beyond the input schema. The schema has 0% description coverage (just titles and types), but the description explains each parameter's meaning, coordinate systems (absolute or relative 0-1), and the duration default value - adding significant value beyond the bare schema.

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 purpose: 'Swipe from one point to another on the screen' - this is a specific verb+action combination. However, it doesn't distinguish this tool from sibling tools like 'gesture' or 'gestures' which might have overlapping functionality, preventing a perfect score.

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. There's no mention of when this swipe action is appropriate versus other interaction methods like 'click', 'long_click', or 'gesture' tools in the sibling list, nor any prerequisites or constraints for its use.

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