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

The description explicitly states the blocking behavior and timeout fallback, which is a critical behavioral trait. Without annotations, it carries the full burden and does so well, though it could mention what happens on timeout (e.g., returns null or error) and if the request is consumed.

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 two sentences: the first delivers the core action and the second provides a concise use-case summary. Every word earns its place, with no redundancy.

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 covers the essential behavior and use case well. However, without an output schema, it doesn't specify the return structure (e.g., fields like method, path, body). Also, default timeout is in schema but not description. Still, it is largely complete for a blocking tool.

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?

The input schema covers all 4 parameters with descriptions, achieving 100% coverage. The tool description does not add new information about parameters beyond what the schema provides, so it meets the baseline score.

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 blocks until a matching hook request is captured, then returns its full detail. It uses specific verbs ('Block', 'return') and resource ('hook request'), and provides a succinct use case that distinguishes it from siblings like get_hook_request or list_hook_requests.

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 gives explicit context with the phrase 'trigger the flow under test, then assert its webhook fired', indicating when to use this tool. It doesn't explicitly exclude alternatives, but the framing strongly implies its specific role in the testing flow.

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