browser_wait

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

No behavioral details beyond the basic action. Does not disclose whether the wait is blocking, if there are any side effects, or limits. With no annotations, the description should provide more transparency.

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?

The description is concise but references another tool (browser_docs) for more info, which is efficient yet slightly less self-contained. Front-loading is good.

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 simple single-parameter tool, the description is adequate but incomplete. It relies on browser_docs for full documentation, and does not specify details like blocking behavior or return values (though no output schema exists).

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?

The input schema already describes the 'ms' parameter as 'Milliseconds to wait' with 100% coverage. The description adds no additional meaning or constraints beyond the schema, so baseline score of 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 clearly states the tool pauses execution for a duration, but does not differentiate from the sibling tool browser_wait_for_selector which is a conditional wait. Reference to browser_docs hints at further documentation but not differentiation.

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?

No guidance on when to use this tool versus alternatives like browser_wait_for_selector or other timing mechanisms. The description lacks context for appropriate usage scenarios.

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