app_wait_for

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

No annotations present; the description discloses polling behavior, timeout, and the wait conditions, but omits details like retries, polling frequency, return value, and timeout error handling.

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 reasonably concise and front-loaded, with a single sentence covering key points, though it could be slightly more terse.

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 or annotations, the description lacks details on return values, error behavior, and polling mechanics, leaving gaps for an agent to use the tool correctly.

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 adds context beyond the schema by explaining mutual exclusivity of text and selector, the meaning of state, and providing use-case examples, complementing the 75% schema coverage.

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 polls the app window until a selector or bodyText condition is met, listing use cases (async loading, toasts, dialogs) and distinguishing it from manual re-polling of app_snapshot.

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 gives explicit guidance to use for async states and as an alternative to manually re-polling app_snapshot, but does not elaborate on when to avoid using it or compare to other siblings.

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