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. It mentions 'configurable timing' which hints at the duration/preDelay/postDelay parameters, but doesn't explain what a swipe actually does (e.g., UI interaction, gesture simulation), whether it requires specific simulator state, or what happens on execution. For a tool with 9 parameters and no annotations, this is insufficient behavioral context.

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 concise with three short sentences that each add value: the core action, coordinate sourcing guidance, and timing capability. No wasted words, and the most important information (what the tool does) comes first.

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 (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's effect, return values, error conditions, or relationships to other tools beyond the single mention of describe_ui. For a UI interaction tool with many parameters, more context is needed.

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 0%, so the description must compensate. It only vaguely references 'configurable timing' and coordinates, but doesn't explain what x1/y1/x2/y2 represent (start/end points), what delta means, what simulatorUuid is for, or units for timing parameters. The description adds minimal 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 action ('Swipe from one point to another') and resource (UI coordinates), making the purpose immediately understandable. It distinguishes from siblings like 'tap' or 'gesture' by specifying a swipe motion, though it doesn't explicitly contrast with similar tools like 'long_press' or 'touch'.

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 clear context for when to use this tool: 'Use describe_ui for precise coordinates (don't guess from screenshots).' This gives practical guidance on parameter sourcing. However, it doesn't specify when NOT to use it or mention alternatives among sibling tools like 'gesture' or 'touch'.

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