Wait before looking again, for pages that are still settling. Clamped to 100–10000 ms.
Wait before looking again, for pages that are still settling. Clamped to 100–10000 ms.
| Name | Required | Description | Default |
|---|---|---|---|
| durationMs | No | Milliseconds to wait; default 2000. |
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 carries the full burden. It usefully discloses that out-of-range values are clamped rather than rejected (100–10000 ms), which is real behavioral information, but it says nothing about whether the call blocks, what it returns, or how it interacts with concurrent loading.
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 short sentences, zero filler, with the purpose front-loaded and the constraint immediately after.
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?
A single optional parameter with full schema coverage and no output schema means little else is required; purpose and bounds are both stated. Only the blocking semantics remain unstated, a minor gap for a sleep tool.
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 coverage is 100% and documents the 2000 ms default, so the baseline is 3. The description goes beyond the schema by giving the accepted range and the clamping behavior for the single parameter, which is genuinely additive.
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?
Specific verb ('wait') plus the condition that motivates it ('pages that are still settling'), which separates it from action siblings like browser_reload or browser_stop_loading. It does not name those siblings explicitly, so an agent must infer the boundary itself.
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?
'Wait before looking again, for pages that are still settling' implies when to use it, but there is no statement of when to prefer an alternative (e.g. browser_stop_loading when the load is hung) and no guidance on choosing a duration.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.