webhook_wait_for_webhook

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

The description explains the basic behavior (start server, wait for POST, return body/headers) but lacks details on blocking nature, timeout defaults, error handling, or port behavior. With no annotations, more behavioral context would be beneficial.

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 concise, two sentences that efficiently convey the tool's action and use cases. It is front-loaded with the key behavior, but could be restructured to include parameter details.

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?

Given the tool's moderate complexity (3 optional params, output schema), the description covers the main behavior but omits critical parameter details and default behaviors. This leaves gaps in completeness.

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 description does not mention any of the three parameters (path, timeout, port). Schema description coverage is 0%, so the description should explain these parameters. The agent is left to infer from parameter names, which is insufficient.

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 starts an HTTP server to wait for a POST webhook and returns the body and headers. It lists specific use cases like payment callbacks and GitHub webhooks, making the purpose distinct and actionable.

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 clear usage contexts (payment callbacks, GitHub webhooks, form submissions). No explicit when-not-to-use or alternatives are given, but given no sibling webhook tools, this is sufficient.

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