delete_batch_webhook

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

Annotations already indicate destructive and idempotent behavior. The description adds valuable context: the irreversible nature, that Mailchimp stops sending callbacks, and HTTP 204 on success with 404 on invalid ID. This increases transparency beyond annotations.

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 with no wasted words. Key information is front-loaded in the first sentence. Every sentence provides necessary details about usage, behavior, and return values.

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 and the presence of annotations and output schema, the description covers most aspects: purpose, irreversibility, consequence, error handling, and return format. The only gap is the optional 'account' parameter, which is not explained.

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 0%, so the description must compensate. It explains the 'batch_webhook_id' parameter well (what it is and how to get it), but the 'account' parameter is not mentioned. Partial compensation leads to a mid-range 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 deletes a batch webhook permanently. It uses a specific verb+resource combination. However, it does not explicitly distinguish this from the sibling 'delete_webhook' tool for regular webhooks, which could cause confusion.

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 a prerequisite: using 'list_batch_webhooks' to obtain the ID. However, it offers no comparison to alternatives (e.g., update vs delete) and no when-not-to-use guidance. This makes it minimally adequate.

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