delete_webhook

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the action is 'Permanently delete' and that it deletes 'every captured request/email', which conveys irreversibility and scope. However, it does not mention any permissions, side effects, or error conditions. The description adds some value beyond the schema but could be more explicit about the destructive nature.

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 and front-loaded. The first sentence states the core action, and the second sentence provides usage context. No wasted words; every sentence earns its place.

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 simplicity (one parameter, no nested objects, output schema present), the description is fairly complete. It explains the destructive scope and usage context. It could mention that the action is irreversible, but the word 'Permanently' already implies that. The output schema exists, so return values need not be described.

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 schema description coverage is 100% (the only parameter, webhook_token, is described as 'Webhook UUID returned by create_webhook'). The description does not add additional parameter semantics beyond what the schema provides. Baseline 3 is appropriate since the schema already documents the parameter well.

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's purpose: 'Permanently delete a webhook and every captured request/email.' It uses a specific verb (delete) and resource (webhook), and distinguishes it from sibling tools like delete_request and delete_all_requests by specifying it deletes the webhook itself along with all captured data.

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 context: 'Use when the user is done with a temp inbox or wants to clean up.' It implies when to use this tool, but does not explicitly mention alternatives or when not to use it. However, the context is clear enough for an agent to select it appropriately.

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