Delete Subscribers By Ids

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description reinforces this with 'Permanently', but it adds nothing about cascade effects (list memberships, bounces, campaign stats), partial-failure behavior if some ids do not exist, or any id-count limit — exactly the behavioral context a destructive bulk tool needs.

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?

One short sentence with zero filler, and the most important qualifier ('Permanently') is front-loaded where the agent will see it first.

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 destructive bulk operation with no output schema, the definition is minimally sufficient — the agent knows what it deletes and that the effect is permanent. It omits what the call returns, how non-existent ids are handled, whether deletion cascades to subscriptions or bounces, and any size limits, which leaves real gaps for a high-risk tool.

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 description coverage is 100% for the single 'ids' parameter, so the schema already documents the array of integer subscriber ids with minItems=1. The description's 'explicit list of ids' restates rather than enriches the schema, so the baseline of 3 applies.

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 specific verb ('Permanently deletes'), a resource ('subscribers'), and scope ('multiple ... explicit list of ids'). Combined with the tool name, an agent can distinguish this bulk-by-ids delete from the single-id sibling (listmonk_delete_subscriber) and the query-based sibling (listmonk_delete_subscribers_by_query), though the description never names those alternatives itself.

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 phrase 'given an explicit list of ids' implies the usage boundary (use when you already have concrete ids rather than a filter), but it never says when to prefer this over delete_subscriber or delete_subscribers_by_query, and gives no prerequisites or exclusions.

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