swipe

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

The description does not disclose any behavioral traits. With no annotations, the burden falls entirely on the description. It fails to mention that swiping is a touch gesture, what device or UI element it interacts with, or potential side effects. This is inadequate for safe agent invocation.

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 one short sentence, which is concise but under-specified. It lacks important context about the operation and tool. Every word should add value, but this sentence is too vague and does not justify its brevity.

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 complexity (27 parameters, no output schema, many sibling tools), the description is extremely incomplete. It fails to explain what the tool does in a meaningful way, omits return values, and does not help the agent understand its role within the toolset.

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 96%, so the schema already documents most parameters. The description adds no new meaning beyond stating 'between two points,' which aligns with the 'from' and 'to' parameters. It does not clarify the other 25 parameters or add context, so it meets the baseline but does not exceed it.

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?

Description states 'Swipe between two points,' which indicates the action and resource (swipe gesture from start to end). It is not a tautology and is somewhat specific, but lacks clarity on what is being swiped (e.g., screen, element) and how it differs from siblings like 'scroll' or 'gesture'. It provides a minimal purpose but could be more precise.

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?

No usage guidelines are provided. The description does not state when to use this tool, when not to, or any prerequisites. There is no mention of alternatives or conditions, which is critical given the many sibling tools with overlapping functionality.

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