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 full burden. It explains the waiting mechanism (XHR/fetch requests, readyState) but omits details like error handling on timeout or what happens if the page never becomes idle. The behavior is adequately described for a wait tool, but lacks depth.

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 concise sentences with no unnecessary words. The first sentence delivers the core action, and the second adds valuable context. Perfectly front-loaded and efficient.

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?

The description is sufficient for a simple wait tool with well-documented parameters and no output schema. However, it could mention timeout behavior or potential exceptions for completeness, but given the simplicity, it meets the minimum viable standard.

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% with each parameter having a default and description. The description adds context about 'quiet period' and 'document.readyState,' but doesn't significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 waits for network idle by monitoring XHR/fetch requests and document.readyState. It provides context for SPAs and async pages, making the purpose unmistakable. It effectively distinguishes from sibling tools like wait_for_element by focusing on network activity rather than element presence.

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?

The description explicitly notes this tool is 'essential for SPAs and pages that load data asynchronously,' giving clear guidance on when to use it. While it doesn't list when not to use it or mention alternatives, the context is sufficient for an AI agent to infer appropriate scenarios.

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