Bulk tag subscribers

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

The annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is partly covered. The description still adds real value beyond them: the concrete blast radius ('delivery, audience membership, published data or irreversible state') and the non-obvious auth constraint that API keys are not supported for this endpoint.

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?

Three short sentences, front-loaded with the action and followed by risk and auth constraints. No filler, though the opening sentence contributes nothing over the title and could be replaced with actual scoping information.

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, nested-payload, open-world mutation with no output schema and zero required params, the description covers risk and auth but omits the practical mechanics: what the taggings entries mean, how null ids are interpreted, batch limits, and what a successful call returns or how partial failures are handled.

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 67%, above the midpoint, so the schema carries most parameter documentation. The description only reinforces the confirm requirement and says nothing about the taggings array items (nullable tag_id/subscriber_id), the callback_url, or the payload/payload_file mutual exclusion, which the schema itself describes.

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's first sentence, 'Bulk tag subscribers,' is a verbatim restatement of the tool title and name. It conveys a verb and resource but does no work beyond the identifier itself, and it does not distinguish this tool from nearby siblings such as tag_subscriber, tag_subscriber_by_id, bulk_create_tags, or bulk_remove_tags_from_subscribers.

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?

There is no when-to-use guidance and no routing to alternatives. The stated conditions ('Requires confirm=true', 'Requires OAuth') are prerequisites, not selection criteria, and nothing tells the agent when to prefer this over single-subscriber tagging or the bulk tag-creation tools.

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