Pause browser automation for up to 60 seconds to wait for page elements or delays between steps.
Sleep up to 60 seconds.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "browser_wait"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| ms | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only says 'Sleep up to 60 seconds,' missing details like blocking behavior, interruptibility, or consequences of exceeding the limit.
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 extremely terse at four words, which is under-specification rather than efficient conciseness. It lacks necessary details to be minimally viable.
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?
Given the low schema coverage, no output schema, and only one parameter, the description is incomplete. It does not explain the unit of measurement, the default, or any constraints, leaving the agent with insufficient information to invoke the tool correctly.
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 schema has 0% description coverage, meaning the description does not explain the 'ms' parameter at all. It fails to add meaning beyond the schema, despite the low coverage needing compensation.
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 sleeps for a duration, which is a specific verb and resource. It distinguishes from sibling tools, which are all browser actions. However, it could be more precise about the unit (milliseconds) and the 'up to' limit.
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 on when to use this tool versus alternatives. While there is no other wait tool among siblings, the description does not provide any context for appropriate usage or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.