Delete Bounce

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description's only addition is the 'single' blast radius, which usefully confirms that exactly one record is affected rather than a batch. It says nothing about whether the removal is permanent, what happens if the id doesn't exist, or required permissions.

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 front-loaded sentence with no filler or redundancy. It is appropriately sized for a one-parameter deletion tool, though it leans toward terse rather than efficiently complete.

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 destructive single-record tool whose annotations and schema are both rich, the definition covers the essentials. It omits return/confirmation behavior and the not-found case, which matter slightly more here because there is no output schema to explain the result.

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% with one required integer described as 'Numeric id.' The description only restates this as 'by id' and adds no format, range, or sourcing guidance (e.g., where to obtain the bounce id). Baseline 3 is appropriate when the schema already fully documents the parameter.

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?

States a specific verb and resource ('Deletes a single bounce record') with the selector ('by id'), which implicitly separates it from the sibling bulk tools listmonk_delete_bounces and listmonk_delete_subscriber_bounces. It stops short of naming those alternatives explicitly, but the scope is unambiguous.

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 word 'single' hints at the bulk alternative, but there is no explicit statement of when to delete one bounce versus using listmonk_delete_bounces or listmonk_delete_subscriber_bounces. No prerequisites, no exclusions, no context about why an agent would remove a bounce record at all.

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