delete_mailbox_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 does add a useful consequence ('new mail stops firing it immediately'), showing an immediate effect, but it does not mention irreversibility, idempotency, error behavior, or what happens if no webhook exists. This is a meaningful but incomplete disclosure for a destructive operation.

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?

A single sentence with no filler. It states the action, the resource, and the immediate behavioral consequence in a compact and readable way.

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 simple two-parameter delete tool with fully documented schema, the description is adequate. It captures the essential effect. It could be stronger by noting whether removal is permanent or by describing the result when no webhook is configured, but these are minor gaps for this tool's complexity.

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 covers 100% of parameters with clear descriptions and examples for both domain and localPart. The description adds no extra parameter-level detail, which is acceptable given the high schema coverage.

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 clear verb ('Remove') and a specific resource ('a mailbox's webhook'), which directly distinguishes it from sibling tools like set_mailbox_webhook and get_mailbox_webhook. There is no ambiguity about what the tool does.

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 clearly implies the use case: when you want to stop a webhook from firing on new mail. It does not explicitly name alternatives or exclusion conditions, but the context and sibling list make the intended purpose obvious.

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