ui_swipe

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

Annotations only indicate readOnlyHint=false and openWorldHint=true, but the description adds no extra behavioral context. It does not disclose coordinate system, effect on the UI, whether the simulator must be foregrounded, or any side effects. The description is purely nominal.

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, succinct sentence with no fluff or redundancy. It front-loads the action and resource, making it easy to scan. Every word earns its place.

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 7 parameters and no output schema, the description is minimal but not entirely insufficient because the schema covers parameter details. However, it lacks high-level behavioral context (e.g., swipe gesture semantics, coordinate units, delta meaning) that would help an agent know exactly what to expect. This is an adequate-but-gappy description.

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 coverage is 100%, with all parameters (x_start, y_start, x_end, y_end, delta, duration, udid) documented in the input schema. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Swipe') and resource ('screen in the iOS Simulator'), making the tool's core action clear. However, it does not differentiate from sibling gesture tools like ui_tap or ui_type beyond the action name, so it stops short of a 5.

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 guidance is provided on when to use this tool over alternatives. There is no mention of scenarios, prerequisites (e.g., booted simulator), or exclusions. The description simply states the action without context.

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