ios_scroll

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

The annotations are neutral, so the description carries the behavioral disclosure. It adds valuable context: scrolling stops as soon as the text appears, gives up when content stops moving, and avoids spinning at the end of a list. This is exactly the kind of runtime behavior an agent needs to know and is not present in the schema.

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 two short sentences with no filler. The core action is front-loaded, and the second sentence supplies critical termination behavior. 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?

The tool is simple, the input schema is fully documented, and an output schema exists. The description covers the main purpose, the optional stopping condition, the give-up behavior, and the anti-spin guarantee. Nothing essential is missing for an agent to call this tool confidently.

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?

The input schema already describes all six parameters, so the baseline is 3. The description adds meaningful semantic detail to the `until` parameter by defining both the success condition and the give-up condition, clarifying what the agent should expect. This goes beyond the schema's terse 'Keep scrolling until this text appears.'

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 ('Scroll') and its optional goal ('until some text comes into view'). It is specific enough about the tool's behavior, but it does not explicitly distinguish ios_scroll from sibling ios_swipe, which might also scroll content.

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 implies usage through the `until` option and explains when scrolling stops, giving the agent a sense of when to use it. However, it does not explicitly state when to prefer this tool over alternatives like swipe, drag, or wait_for, nor does it mention when not to use it.

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