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

With no annotations provided, the description carries the full burden. It conveys that the tool blocks until a condition is met, but it does not disclose behavior on timeout (e.g., whether it throws or returns a status) or any side effects. The front-loaded behavioral details are useful but not exhaustive.

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?

Three sentences, no fluff. The first sentence states the core function and scoping, the second gives a preference over an alternative, and the third handles device routing. Each clause 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?

For a wait tool with 5 paramsched and no output schema, the description provides the main context: desktop scope, pageId, condition types, and timeout default is in schema. Missing details like timeout failure behavior or how to trigger a pure delay are minor gaps, but overall it is complete enough for an agent to invoke 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 coverage is 100%, so parameters are already well-documented in the schema. The description maps high-level concepts ('appear or disappear', 'text to show up', 'fixed delay') to the parameters but adds no new syntax or caveats beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('Wait'), a specific resource ('DESKTOP grid browser'), and a requirement ('by pageId'). It enumerates exact condition types (element appear/disappear, text shown, fixed delay) and explicitly differentiates from siblings (web_evaluate, webpage_wait_for).

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 instructs to prefer this tool over polling with web_evaluate, and directs mobile/tablet usage to webpage_wait_for by udid. This gives clear when-to-use and when-not-to-use guidance, including a named alternative.

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