Scroll Until

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

No annotations are provided, so the description carries the full disclosure burden and largely fails it. It reveals only that the call ends with a node or null; it does not say that it performs repeated swipe gestures, whether it alters screen state, what happens on timeout, or side effects of scrolling the UI.

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?

A single compact sentence with the core behavior front-loaded and no filler. It is efficient, though its brevity is more under-specification than true economy for a 9-parameter looping tool.

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?

An output schema exists, so the return format need not be re-explained, but the tool is a multi-swipe loop with 9 undocumented parameters and no annotations. For that complexity the description leaves far too much undefined for an agent to call it 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?

Nine parameters with 0% schema description coverage, and the description names none of them. 'Matching node' vaguely implies the match criteria exist but gives no clue about the relationship between text, text_contains, any_contains, and resource_id, nor the meaning of settle, distance, direction, or max_swipes.

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?

States a specific verb and resource: scrolling until a matching node appears, and even names the return value (node or null). It does not differentiate itself from close siblings like scroll_to, find_nodes, or wait_for_nodes, which an agent must pick between, 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?

There is no guidance on when to use this versus the many alternatives in the sibling list (scroll_to, scroll_down, wait_for_text, find_nodes). The only hint is the tool name itself implying a loop-until-found semantics, which the agent must infer.

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