browser_wait

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether waiting blocks execution, what happens if the text/selector never appears, whether there is a timeout or error, or which condition wins when both ms and a condition are supplied.

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?

A single compact sentence that front-loads the core action and covers both operating modes without filler. Nothing is wasted.

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?

With no annotations, no output schema, and three optional parameters, the definition is too thin. Missing timeout/error behavior and parameter precedence leaves real gaps for correct invocation of a synchronization primitive.

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 only 33%; only 'ms' has a description with its default. The description partially compensates by explaining that 'text' and 'selector' are conditions to wait for, but adds no detail on matching semantics (exact vs substring, CSS vs XPath) or precedence between the three parameters.

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) and both modes of operation: a fixed duration or a condition (text/selector appears). It is immediately distinguishable from siblings like browser_click or browser_snapshot, though it does not explicitly name alternatives.

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?

There is no guidance on when to prefer this over alternatives such as browser_snapshot or browser_find for detecting page state, nor any prerequisites or context. The agent must infer from the name alone that this is for synchronization.

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