wait_for_request

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

With no annotations, the description carries the full burden, and it does disclose blocking semantics and substring-matching behavior rather than restating the tool name. However, it omits timeout behavior, what happens if no request matches, and return/error details, all of which matter because there is no output schema.

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 compact sentences place the core blocking behavior first, followed by the sibling contrast and the use case. There is no filler, repetition, or unnecessary detail.

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 simple wait tool, the description covers purpose, matching rule, and sibling selection, while the schema covers parameter definitions. The missing timeout/error behavior and return value are notable because there is no output schema or annotations, but the low complexity keeps the gap moderate.

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 33%, so the description needed to compensate for undocumented parameters. It usefully clarifies url_pattern as a substring match, but says nothing about timeout semantics or units, and only repeats the schema's one-line method filter without adding 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 names a specific behavior ('Block until the page ISSUES a request matching a URL substring') and explicitly contrasts itself with wait_for_response. The use-case sentence further clarifies it confirms an API call actually fired, making it easy to distinguish from siblings.

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 gives the primary use case ('Use it to confirm an action actually fired its API call') and names the closest alternative (wait_for_response) as the reply-oriented counterpart. It does not explicitly contrast with the other wait-family siblings like wait_for_url or wait_for_navigation, so exclusions are incomplete.

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