wait_for_response

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates that the tool waits for a network response; it does not disclose timeout behavior, rejection on timeout, whether this tool initiates the request, or what the returned value is.

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 focused sentence with no filler, and the core behavior is front-loaded. It loses points only because the brevity leaves out important behavioral context rather than because of verbosity.

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?

There is no output schema and no annotations, so the description should clarify what happens after the wait succeeds or times out. An agent invoking this tool does not know what the response looks like, whether a failure throws, or whether the wait is interruptible, making the definition incomplete for correct invocation.

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 only 50%, with timeout lacking any schema documentation. The phrase 'URL pattern' largely duplicates the existing 'URL substring to match' description and adds no detail about timeout units, default behavior, or pattern syntax, failing to compensate for the undocumented parameter.

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 states a clear operation and resource: waiting for a network response matching a URL pattern. It is specific enough to differentiate from related siblings like wait_for_navigation or wait_for_network_idle, and the 'response' wording distinguishes it from wait_for_request.

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 sentence implies the tool should be used when the agent needs to block until a particular network response is seen. However, it does not explicitly say when to prefer this over wait_for_request, wait_for_network_idle, or wait_for_any_of, nor does it mention that the triggering request/action should already be started elsewhere.

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