Blocklist Subscribers (Bulk 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 description gets a lower bar. It does add real context — that blocklisted subscribers stop receiving campaign sends — but omits reversibility (is there an unblocklist?), what happens to existing list memberships, and how nonexistent ids are handled.

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; the trailing clause about campaign sends earns its place by explaining effect. Slightly more efficiency could come from naming the batch limit or the by-query alternative in the same sentence.

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 one-parameter tool whose safety profile is fully covered by annotations, this is close but not complete: no batch-size limits, no note on partial success with invalid ids, and no hint about downstream effects on list membership or reversibility.

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?

Only one parameter, and the schema already documents it fully ('Subscriber ids to blocklist') at 100% coverage. The description restates that these are subscriber ids without adding format, batch-size, or duplicate/validation semantics, so baseline 3 is appropriate.

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 (blocklist) and resource (an explicit set of subscribers by id), plus the effect. The 'explicit set ... by id' phrasing implicitly distinguishes it from listmonk_blocklist_subscribers_by_query and the single-item listmonk_blocklist_subscriber, though neither sibling is named.

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 by-id framing hints at when this tool applies versus query-based or single-subscriber blocklisting, but no explicit when-to-use, when-not-to-use, or alternative is offered. An agent must infer the selection rule from the parameter name alone.

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