adb_scroll_until

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

With no annotations, the description discloses the iterative process: swipe, check UI hierarchy, repeat until found or max iterations. It also mentions the tapWhenFound option. It does not detail failure behavior (e.g., returns null), but covers the core loop transparently.

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 three sentences, front-loading the main action. Every sentence adds value: first states purpose, second explains the loop, third gives use case. No fluff.

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 no output schema and no annotations, the description covers the essential behavior. Minor gap: what happens if element not found (e.g., returns empty or error). But overall complete for the tool's purpose.

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 baseline 3. The description adds no additional meaning to the parameters beyond the schema's descriptions (e.g., 'text' case-insensitive, 'direction' enum).

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 to find a target element, distinguishing it from sibling tools like adb_ui_find (no scrolling) and adb_input_fling (no element checking). It uses specific verbs 'scroll' and 'find' with the resource 'screen' and 'UI hierarchy'.

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 context by stating it is 'useful for finding elements in long lists or scrollable content', which guides when to use. However, it does not explicitly mention when not to use or list alternatives, though the sibling list implicitly provides options.

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