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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description usefully adds the 25-second cap and the shape of the returned payload (headers, body, truncation flag), but it never says what happens when no request matches within the timeout, which is the single most important behavioral trait for a blocking tool.

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 dense sentences with zero filler; the wait duration and resource are front-loaded before the filter list and return shape. Every clause carries information.

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?

With no output schema, the description correctly carries the return-value burden (headers, body, truncation flag). It is nearly complete for an 8-parameter polling tool; the gap is the unstated timeout/no-match outcome.

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%, so the baseline is 3. The description goes beyond the schema by stating that header_name matching is case-insensitive (the schema only says 'Optional HTTP header name') and by framing since as an RFC3339 lower bound, though it omits timeout_seconds entirely.

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 specific verb (wait), resource (captured HTTP request), and blocking scope (up to 25 seconds), which cleanly separates it from read_request and list_requests. It does not, however, name any sibling explicitly, so the differentiation is inferential rather than stated.

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 blocking semantics imply the use case (poll for an inbound request rather than inspect already-stored ones), but there is no explicit statement of when to prefer this over read_request, list_requests, or wait_for_email. Usage is implied, not guided.

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