Wait until the UI settles

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

Describes polling mechanism, structural digest, and timeout behavior. Annotations confirm read-only, no contradictions. Description adds valuable detail beyond annotations.

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 concise sentences: first explains operation, second states usage. No fluff, front-loaded with key behavior.

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?

Adequately explains behavior for a simple polling tool with optional parameters. No output schema, but return condition (stable or timeout) is clear. Could mention what happens on timeout.

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 has 100% coverage with clear descriptions. Description ties 'stableSamples' to 'N consecutive identical dumps', adding context. Could elaborate more on 'serial' default behavior.

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?

Description clearly states it polls UI dumps and returns when stable or timeout. Distinct from siblings like devilge_wait_for_text (waits for element) and devilge_dump_ui (single dump).

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 says 'Useful between a tap and the next action to absorb animations / asynchronous updates without sleeps.' Provides clear usage context but could mention alternatives more directly.

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