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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool blocks before continuing, supports element visibility, text appearance, and fixed delays, and is scoped to desktop browser pages. It does not explain timeout failure behavior or what happens after the wait, but the timeoutMs parameter provides partial context. Overall, the core behavior is transparent.

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 concise and well-structured: it states the purpose, lists supported conditions, and gives alternatives in three sentences. Every sentence adds value, and the most important scoping and guidance appear early. No filler or repetition.

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?

For a relatively simple wait tool, the description covers the primary use case, platform scope, alternatives, and condition types. The main gap is the fixed-delay claim not being clearly tied to a schema parameter, which could confuse an agent reading the schema. Otherwise, the description is sufficient for correct tool selection and invocation.

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 already documents all five parameters with 100% coverage, so the baseline is 3. The description adds useful framing by mapping pageId to the desktop browser and mentioning condition categories, but it does not clarify how a 'fixed delay' is expressed in parameters (no delayMs field exists, so it likely relies on timeoutMs with no selector/text). This slight mismatch prevents a higher score.

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 ('Wait for a condition') and the specific resource ('DESKTOP grid browser (by pageId)'). It enumerates the condition types (appear, disappear, text, fixed delay), and it differentiates this tool from web_evaluate and webpage_wait_for. An agent can immediately understand what this tool does and how it differs from nearby siblings.

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 provides explicit usage guidance: 'Prefer this over polling with web_evaluate' and 'for a phone or tablet use webpage_wait_for (by udid)'. This tells the agent when to choose this tool and which alternative to use instead. No ambiguity remains about the intended context.

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