android_scroll_to

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

The description mentions 'bounded steps' and 'UI stops changing', giving some insight into iterative behavior and termination criteria. However, it does not explain side effects, failure behavior, or how it interacts with the destructiveHint annotation, which remains unexplained.

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 a single, concise sentence with no redundant info. It follows a clear structure but could be slightly more specific about the selector criteria without becoming verbose.

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 description is minimal and does not cover important context such as default selector matching behavior, timeout handling, or what constitutes a 'bounded step'. Given the high parameter count and no output schema, this leaves significant gaps.

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 description provides no mapping between the 15 parameters and the concept of a 'semantic selector'. Since the schema has zero descriptions, the description fails to compensate and leaves parameter meaning ambiguous.

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 the termination condition (until a semantic selector becomes visible or UI stops changing). However, the term 'semantic selector' is vague and not explicitly tied to the parameter set, so it could be clearer.

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 does not provide any guidance on when to use this tool versus alternatives like android_scroll or android_ui_find. It implies usage for scroll-to-element scenarios but does not state explicit conditions or exclusions.

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