browser_wait_for_network_idle

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

No annotations are provided, so the description carries the full behavioral burden. It defines the idle condition, which is useful, but omits what happens on timeout (error vs. silent return), whether it blocks the tab, and what the result indicates. For a blocking wait tool, this leaves significant gaps.

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?

A single front-loaded sentence with no filler; the condition is stated immediately. It is perhaps too terse for a blocking operation, but nothing is wasted.

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?

With no annotations, no output schema, and 0% parameter coverage, the description should carry much more. Timeout semantics, tab targeting, and return behavior are all missing, leaving the agent unable to predict call outcomes.

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 description coverage is 0% across 3 parameters. The description partially clarifies idle_ms by tying it to the 'no new resources started' window, but tab_id (which tab, default active?) and timeout (units, behavior on expiry) are entirely undocumented in both schema and description.

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?

States a specific verb (wait) and a precise condition (no new network resources started for idle_ms), which distinguishes it from other wait siblings like browser_wait_for_url or browser_wait_for_element. However, it doesn't explicitly name those alternatives, so the differentiation is implied by the condition rather than stated.

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 versus browser_wait_for_url, browser_wait_for_element, browser_wait_for_result, or browser_sync_barrier. No mention of prerequisites or typical sequencing (e.g. after navigation, before reading DOM). The agent must infer usage entirely.

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