adb_scroll_until

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

With no annotations, the description fully carries the burden, detailing the swipe gesture, UI hierarchy check, and loop until found or max iterations. It could add more about side effects or post-condition state, but is fairly transparent.

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?

Three sentences, front-loaded with the main action, no redundant information. Every sentence adds value.

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 tool complexity (multiple matchers, direction, max scrolls, tap option, no output schema), the description covers the essential loop and behavior. It could mention handling multiple matches or direction semantics, but is sufficiently complete.

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%, so the schema already describes parameters. The description adds minimal parameter meaning beyond the schema, not explaining how to combine matchers or that at least one is needed. Baseline 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 clearly states the tool scrolls repeatedly until a target element is found, with a specific verb and resource. It distinguishes from siblings like adb_tap_element (tap), adb_ui_find (find without scroll), and adb_wait_element (wait without scroll).

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 explains the tool is useful for long lists or scrollable content, providing clear context. However, it does not explicitly state alternatives or when not to use, such as comparing to adb_input_drag for manual scrolling.

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