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 usefully discloses the two waiting mechanisms and a concrete seconds format, but is silent on the most important behavioral trait for a wait tool: what happens on timeout (error, silent return, or hang) and whether the call blocks.

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 an inline example; every clause carries information and nothing is padded.

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?

An output schema exists, so return values need not be explained, and the two wait modes are covered. However, for a tool whose correctness hinges on timeout/error behavior and on which tab is targeted, both omissions leave real gaps.

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 the description must compensate. It does explain the dual semantics of target_or_seconds with an example ('2.5'), which the schema alone does not, but it says nothing about tab_index, leaving one of two parameters entirely undocumented.

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) and two concrete resources/conditions (a duration in seconds, or a CSS/text selector appearing), which is far more specific than the bare tool name. It does not, however, differentiate itself from siblings such as browser_get_content or browser_evaluate that an agent might reach for when waiting for content.

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 dual-mode description ('wait for seconds ... or wait for a CSS/text selector to appear') implicitly tells the agent this is the tool for synchronization before reading or clicking. There is no explicit when-not, no timeout guidance, and no named alternative (e.g. browser_evaluate) for more complex waits.

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