ios_swipe

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

Annotations already cover read-only, idempotent, and destructive hints, so the description doesn't need to restate safety. The phrase 'Swipe once' adds one-shot gesture semantics, but the description doesn't detail side effects like navigation or reveal behavior beyond that.

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 a single, front-loaded sentence with no wasted words. It communicates action, scope, and usage contexts efficiently.

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 low-complexity gesture tool with a complete schema, annotations, and an output schema, the description provides sufficient orientation. A more explicit boundary against ios_scroll would make it fully complete, but that's a minor gap.

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 100%, so the parameters are already documented with meaningful descriptions. The tool description adds no parameter-level guidance, which matches the baseline for fully covered schemas.

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 names a specific gesture ('Swipe once') and scopes it to concrete UI contexts (carousels, page views, swipe-to-reveal rows), which differentiates it from siblings like ios_scroll and ios_drag in practice. It doesn't explicitly name another tool, but the use-case list provides clear enough purpose.

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 gives clear contexts where the tool is appropriate, so an agent can infer when to select it over similar gesture tools. It stops short of saying when not to use it or naming alternatives, so it doesn't reach the explicit when/when-not bar.

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