swipe

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

No annotations are provided. The description discloses that it simulates a touch swipe and requires a mobile viewport, but does not address error behavior (e.g., what happens if viewport is not set) or return values. Basic behavioral context is given, but more detail would improve transparency.

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 two sentences: the first states the core action and parameters, the second gives a prerequisite. It is tightly written with no wasted words and places the most important information upfront.

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 5 parameters (2 required), nested objects, and no output schema or annotations, the description adequately covers the tool's purpose, prerequisites, and parameter roles. It lacks details on return values or error handling, but for a simple gesture tool, it is largely complete.

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 input schema has 100% coverage with descriptions for all parameters. The tool description adds only framing (e.g., 'from point A to point B') beyond the schema. With full schema coverage, baseline is 3, and the description provides minimal extra semantic value.

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 'Simulate touch swipe from point A to point B with duration,' specifying the verb, resource, and parameters. Among sibling tools like 'double_tap', 'long_press', and 'pinch', it uniquely identifies a swipe gesture.

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 explicitly advises to ensure a mobile/touch-enabled viewport via 'emulate_device' or 'resize_viewport' before using this tool. It does not mention when to avoid using it, but the prerequisite is clear and helpful.

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