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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the blocking semantics of the conditions, but omits two behaviors an agent would care about: that the call produces a page snapshot afterward (visible only in the snapshot param as 'page view after the action') and what the tool does when the timeout expires — error versus silent return.

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, front-loaded with the resolution conditions before the comparative advice. No filler or restated name/title.

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 an 11-parameter tool with no output schema, the description leaves the agent guessing about the return payload (snapshot diff default), timeout failure behavior, and how multiple condition params interact if more than one is supplied. Adequate to invoke, not complete.

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 64%, so baseline is 3. The description does group the condition parameters (text/text_gone/ref/selector/url) and implies exclusivity via 'use one text condition', which is real meaning beyond the schema; however it never mentions timeout, snapshot, or secret, and 'the URL changes' is looser than the actual url_contains substring semantics.

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?

States a specific verb (wait) with the exact conditions it resolves on: text appearing, text_gone disappearing, ref/selector becoming visible, or URL change. The contrast with 'fixed delays' carves out a clear niche against the ms parameter and against naive polling, though no sibling tool (e.g. act, snapshot) is named as an alternative.

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?

'Use one text condition' is an explicit invocation constraint, and 'Better than fixed delays' tells the agent when to prefer this over a plain ms sleep. It stops short of stating when-not-to-use it (e.g. when act already auto-waits) or what happens on timeout expiry.

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