browser_wait_for_response

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the high-level action, omitting critical behavioral details such as timeout semantics (throws or resolves?), matching criteria (regex against status code, headers, or body?), and what happens if no matching response occurs. The description adds nothing beyond the basic action, leaving users to guess at the tool's inner workings.

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 a single, concise sentence of six words. It is front-loaded with the primary action, contains no filler, and every word contributes to the core purpose. This is exemplary conciseness with zero waste.

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?

For a tool with no annotations, no output schema, and two parameters including a regex pattern and timeout, the description is too sparse. It fails to explain return behavior, error conditions, or how the URL pattern is applied (e.g., exact match vs substring). The tool is moderately simple, but the lack of behavioral and output context leaves significant gaps for an agent attempting to use it 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?

Schema description coverage is 100%, so both parameters (urlPattern as a regex string, timeout with default of 30000 ms) are already documented. The description's phrase 'matching URL pattern' essentially restates the urlPattern parameter without adding new semantics. This meets the baseline of 3 for high schema coverage but does not elevate the meaning.

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 'Wait for network response matching URL pattern' has a specific verb ('wait for') and resource ('network response'), with a clear qualifier ('matching URL pattern'). It distinguishes itself from sibling tools like browser_wait_for_load, browser_wait_for_selector, and browser_wait_for_navigation by targeting network responses rather than page loads, DOM elements, or navigation events.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or alternative tools such as browser_wait_for_navigation or browser_wait_for_selector. The only usage context is implied by the purpose statement itself, which is too weak to count as meaningful guidance.

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