browser_wait_for

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

The description adds some functional context (what it waits for) but does not disclose important behavioral details like timeout handling, error conditions, or what happens if the expected text never appears. Annotations already indicate read-only and non-destructive nature.

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, concise sentence that directly states the purpose without unnecessary words or structure.

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?

The description lacks critical context about timeout behavior, return values, or how to handle situations where the condition is not met. Given its simplicity, more detail on operational expectations would improve completeness.

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 parameter descriptions in the schema are already explicit. The tool description adds only the general notion of three separate wait modes but does not clarify interactions or precedence when multiple parameters are provided, so it offers minimal additional meaning.

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's action (wait) and the objects (text appear, disappear, or time pass). It is distinct from sibling tools that perform other browser actions.

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 description implies when to use this tool (when needing to wait for a condition in the browser) but does not explicitly contrast it with alternatives or provide usage scenarios.

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