swipe

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

Discloses that direction is content movement, full-screen swipe, mobile-only, and no error on impossible scroll. Annotations indicate non-destructive (destructiveHint: false), consistent with description. No contradictions.

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?

Three sentences, tightly written with no extraneous information. Front-loaded with the core action, then usage guidelines and behavior in subsequent sentences.

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 simple gesture tool, the description covers purpose, usage alternatives, parameter details, and behavioral notes. No output schema needed; everything is well-addressed.

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 has 100% coverage with descriptions for all parameters. Description adds context about direction meaning and default percent values, enhancing understanding beyond 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 it performs a full-screen swipe gesture, specifies direction meaning (content movement), and distinguishes from sibling tools like scroll and drag_and_drop. It also notes mobile-only usage.

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?

Explicitly tells when to use alternatives: 'For browser scrolling use scroll; for dragging a specific element use drag_and_drop.' Also mentions no error if content cannot scroll further, guiding appropriate usage.

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