adb_wait_stable

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

No annotations are provided, so the description carries full burden. It explains the polling mechanism and stability condition but does not disclose the return value, error handling, or side effects. The description is adequate but not comprehensive.

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?

Extremely concise: three sentences that each add distinct value. The first states the main purpose, the second explains the mechanism, and the third provides usage context. 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?

The description explains when to use the tool (after screen changes) but does not compare with sibling tools like adb_wait_element. It lacks details on return values or behavior on timeout/failure, leaving some gaps for an AI agent.

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 covers 100% of parameters with descriptions, so the description adds little extra meaning beyond the schema. It provides a high-level context but does not enhance the understanding of each parameter.

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's purpose: to wait for the UI to stabilize by polling the UI hierarchy until consecutive dumps are identical. The verb 'wait' and resource 'UI' are specific, and the mechanism is distinct from sibling tools like adb_wait_element.

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?

Explicitly mentions appropriate contexts: after screen transitions, animations, or content loading before interacting with elements. However, it does not describe when not to use it or suggest specific alternatives, though the context is clear.

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