browser_wait

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

With no annotations, the description carries the full burden and discloses nothing about blocking behavior, whether the wait is fixed or condition-based, any maximum duration, or whether it throws on timeout. For a timing primitive whose main risk is hanging an automation loop, that is a real gap.

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 short sentence with no filler, and the key information (the seconds unit) is front-loaded. It is efficient but too thin to earn full marks.

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, no-output tool the essential facts are present, so nothing blocks invocation. Still, the absence of annotations and of any statement about return value or blocking semantics leaves the agent without enough context to use it confidently in a browser automation flow.

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 schema already documents "Wait duration in seconds", so the description's "in seconds" adds nothing new. It does not say whether fractional seconds are accepted or what bounds apply. Baseline 3 applies when the schema does all the work.

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 verb and unit ("Wait ... in seconds"), but it largely restates the tool name and its single parameter. It gives no hint about how this differs from other timing behaviors implied by siblings such as browser_press_key or browser_navigate.

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 when-to-use guidance: no mention of waiting after navigation, before a screenshot, or as an alternative to polling for an element. The agent must guess the intended scenario.

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