webhook_test

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

No annotations exist, so description bears full burden. It discloses HTTPS POST with HMAC/retry/circuit-breaker, off-by-default, side effects (outbound POST), return values, and that 'delivered' means attempted delivery only. Also references ADR for logging behavior.

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?

Description is efficiently structured with purpose first, followed by operational details, warnings, return info, notes, and example. No filler; each sentence adds value.

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 single-parameter testing tool with no output schema, the description covers all necessary aspects: purpose, mechanics, prerequisites, constraints, return format, side effects, and an example. No gaps.

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%, baseline 3. Description adds example usage and clarifies the parameter's role beyond the schema description. While not necessary, the example enhances understanding.

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 fires a synthetic event through a registered webhook to verify wiring. It distinguishes from sibling tools like webhook_register and webhook_list by focusing on testing. The verb 'fire' and resource 'webhook' are specific.

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?

Explicitly states when to use (verify webhook wiring) and when not to use (load testing). Mentions prerequisite environment variable. Does not require alternative tool mention as siblings are distinct.

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