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 does not disclose whether timeouts throw errors, what happens when a selector never appears, the default/max timeout behavior, or any side effects; it mostly restates the enum modes.

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 that lists the supported wait conditions with no wasted text. It is appropriately sized for the core purpose.

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 browser wait tool with no annotations, no output schema, and low parameter coverage, the description omits failure semantics, parameter coupling, and timeout behavior. An agent lacks enough information to call it correctly in edge cases.

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 only 33%, and the description does not explain how the 'value' parameter should be interpreted for each wait type or what role 'timeout' plays relative to the default. 'value' and 'timeout' remain underdocumented across schema and description.

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 four wait conditions (selector, navigation, networkidle, timeout), clearly distinguishing it from browser action siblings like click or navigate. It lacks explicit comparison to alternatives, so it falls short of a 5.

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 phrase 'before continuing' implies when to use it, but there is no explicit guidance on choosing between wait types or when to avoid waiting. The usage context is present but left largely to inference.

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