browser_wait

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

Discloses default (1000ms) and max (30000ms) limits, which is useful behavioral context beyond the bare schema. No annotations provided, so description carries the burden well.

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?

Two sentences, no wasted words. Action and constraints are front-loaded. Every sentence adds value.

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 parameterless-action tool with no output schema, the description covers purpose, usage context, and parameter details. Complete and sufficient.

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?

Single parameter 'ms' has no schema description (0% coverage), but the description provides meaning: unit (milliseconds), default, and max. Fully compensates for schema gap.

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?

Clearly states the tool waits/pauses for a specified milliseconds before the next action. The verb 'wait' and resource 'time' are explicit, and it distinguishes from sibling tools like 'browser_wait_for_download'.

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?

Provides context for when to use (animations, AJAX, page transitions) but does not explicitly exclude cases or mention alternatives. Still clear enough for appropriate use.

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