browser_wait

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that, not saying whether the call blocks the browser session, whether it can be interrupted, or what happens at the boundary values.

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 sentence with zero waste and the essential detail (seconds) front-loaded. Nothing could be trimmed without losing information.

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 one-parameter, fully documented, annotated tool this is minimally adequate. The notable missing piece is differentiation from browser_wait_for, which shares a nearly identical name and sits in the same 22-tool browser family.

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 100% and the single parameter documents units, minimum 0, and maximum 300, so the schema carries the full burden. The description's "in seconds" merely restates the schema, so baseline 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?

"Wait for a specified time in seconds" gives a clear verb and resource, and the word "time" distinguishes it conceptually from browser_wait_for's condition-based wait. However, it never names or contrasts with that sibling, so the agent must infer the difference from the tool name alone.

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 when-to-use guidance, no mention of when a fixed delay is preferable to browser_wait_for's condition polling, and no note about blocking behavior during the wait. The agent gets no routing help between the two wait tools.

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