browser_wait

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the behavioral trait that the tool pauses and then re-observes, but it leaves the wait duration vague ('a moment'). No contradiction with annotations is present.

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 no filler, and the main action appears immediately. It is appropriately sized for a zero-parameter utility tool.

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 zero-parameter, read-only wait-and-observe tool, the description covers the core behavior and implies the result is an observation. It could be more precise about the wait length and whether the output mirrors browser_observe, but these are minor gaps for a tool this simple.

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 tool has zero parameters and no required inputs, so parameter documentation is unnecessary. Schema coverage is vacuously complete, and there is no parameter information the description would need to add.

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 names a clear action chain: wait a moment, then observe again, which tells the agent the tool introduces a delay and produces a fresh page observation. It is distinguishable from browser_open and browser_close, but it does not explicitly differentiate itself from browser_observe, which also produces observations.

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 gives no guidance about when to use browser_wait instead of browser_observe or other siblings, nor does it mention waiting for dynamic content to settle before acting. The agent must infer usage from the tool name and workflow context.

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