browser_wait_for_network_idle

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers almost nothing: it does not say whether the call blocks, what happens when timeout_seconds elapses (error vs. silent return), or whether idle means zero in-flight requests plus a quiet period. For a timing-sensitive wait tool this is a significant gap.

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, which is structurally clean, but for a tool with five parameters and no other documentation it is under-specified rather than genuinely concise.

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?

An output schema exists, so return values needn't be described, but the definition still leaves timeout semantics, idle definition, and four of five parameters undocumented with no annotations to fall back on. Only the required session_id and the defaults make a minimal call safe.

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?

Five parameters with 0% schema description coverage, and the description explains none of them. Cryptic fields like idle_ms and max_inflight (default 0) are left entirely undefined, so an agent cannot reason about how to tune the wait window versus the timeout.

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') plus a precise resource ('in-page network activity is idle'), which is genuinely distinct from the other wait siblings (selector/url/text/function). It does not, however, explicitly contrast itself with browser_wait or the polling variants, so an agent must infer the difference from the name alone.

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 statement of when to prefer this over browser_wait, browser_wait_for_function, or browser_network_capture_*. No prerequisite or sequencing advice (e.g. call after clicking a navigation trigger) is given.

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