iphone_swipe

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

With no annotations, the description carries the full behavioral burden and does little: it never says whether the swipe is instant or flings with inertia, what coordinate space the points live in (screen points vs pixels), or that the swipe acts on whatever is currently on screen. The 'then'-chaining behavior is only disclosed in the schema, not the description.

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?

Two short sentences with the core action first and the directional tip second; nothing is wasted. It is terse to the point of being sparse, but every sentence 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?

For a 9-parameter gesture tool with conditional follow-up behavior and no annotations or output schema, the description covers the action and one scrolling recipe but omits gesture dynamics, coordinate frame, and screen-state assumptions. The schema fills in the 'then*' parameters, which keeps this from being inadequate.

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 44% and the four coordinate parameters have empty schema descriptions, so the description's note that from_y > to_y means swiping up adds real meaning beyond the schema. However it leaves seconds (gesture duration) and the x-axis untouched, so it only partially compensates for the coverage gap.

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 states a specific verb and resource: swipe from one point to another, with point coordinates. It is clearly distinguishable from siblings like iphone_tap and iphone_long_press by the gesture type, though it never names those siblings explicitly.

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?

It gives one concrete usage recipe (to scroll down, make from_y large and to_y small), which is genuinely helpful directional guidance. It offers no when-not guidance, no prerequisites (app must be foreground?), and no comparison to alternative gestures such as tap or press_button.

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