browser_wait_for

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: it doesn't say whether the call blocks, what it returns on success (element handle, boolean, nothing), or what happens when the timeout expires (error vs. false). 'Target tab' implies an implicit tab context that is never defined.

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 front-loaded sentence with zero filler, which is structurally sound. Its brevity borders on under-specification, but nothing is wasted or buried.

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/polling tool with no annotations and no output schema, the description should at minimum cover return value, default timeout and failure mode. None of that is present, and the implicit tab targeting is undefined, so an agent cannot call this confidently in a multi-tab session.

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 description coverage is 0%, so neither parameter is documented in the schema. The description clarifies 'selector' as a CSS selector, but 'timeoutMs' is never mentioned — no default, no units confirmation, no behavior on expiry — leaving a required-looking tuning parameter entirely unexplained.

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 condition ('until a CSS selector exists'), which is unambiguous and clearly distinct from action siblings like browser_click or browser_type. It doesn't explicitly contrast with polling alternatives such as browser_snapshot or browser_status, but the wait semantics are self-evident.

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 use this versus re-reading the page with browser_text/browser_snapshot, nor any prerequisite context about which tab is 'target' or how it is chosen. The agent is left to infer all usage conditions.

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