Wait for Screen to Settle [Pro]

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

No annotations are provided, so description fully handles transparency. It explains the polling mechanism: polling until two consecutive snapshots are identical. This discloses the behavioral trait of waiting for stability, which is valuable for an agent to understand potential time consumption.

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?

Two sentences, no filler. The first sentence states the purpose, the second explains the mechanism and usage. Every sentence earns its place.

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 annotations, the description is fairly complete. It explains what the tool does, how it works, and when to use it. A minor gap: the description does not mention what happens on timeout (e.g., error or return), but overall it's sufficient for an agent to use 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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the purpose of timeout and poll_interval in context of polling, though the schema already describes them. The justification for these parameters is slightly enhanced by the behavioral context.

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 waits for the UI to stop changing after navigation or action, which is a specific verb+resource purpose. It distinguishes from siblings like wait_for_element by specifying it waits for the entire screen to settle, not a particular 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?

The description explicitly recommends use after tapping navigation buttons or screen transitions. It does not explicitly state when not to use it or alternatives, but the context of polling for identical snapshots implies it's for dynamic screen updates, which is clear enough.

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