browser_wait_for_timeout

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

With no annotations, the description carries the full burden. It only restates what the tool does without revealing behavioral details like blocking behavior, return value, or error conditions. The description adds no context beyond the name and schema.

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 a single, short sentence with zero wasted words. It is appropriately sized for such a simple tool and front-loads the core action.

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 one-parameter tool, the description plus schema is adequate for basic invocation. However, it lacks any usage context or differentiation from conditional wait tools, which may cause confusion in tool selection.

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 100% for the single parameter, so the baseline is 3. The description does not add any additional semantics beyond referencing 'specified time' which aligns with the schema's 'Milliseconds to wait.'

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 performs a wait for a specified duration, which is a specific verb+resource. It is distinct from sibling wait tools that wait for conditions (e.g., browser_wait_for_load, browser_wait_for_selector) because this one waits for a timeout duration.

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 is provided on when to use this tool versus the many conditional wait tools in the sibling list. There is no mention of alternatives, exclusions, or use cases such as 'use this to add a fixed delay.'

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