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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation. The description adds useful context that it can affect either explicit subscriber ids or every subscriber matching a filter, but it omits the 10,000-subscriber cap and does not elaborate on the effects of bulk unsubscription.

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 a single efficient sentence that front-loads the core operation and then gives the two targeting modes. Every clause contributes to understanding the tool, with no repetition or noise.

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 7-parameter bulk write tool with no output schema, the description is adequate but thin. It captures the main targeting modes but leaves the agent to rely on the schema for limits, filter fields, and the exact meaning of all_matching.

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 moderate (57%), and the description explains the central ids-versus-filter targeting distinction plus an example tied to engagement. It still does not clarify the search, subscribed, or all_matching semantics beyond what the schema already provides, and the required action parameter is only implied by 'subscribe or unsubscribe'.

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 pair (subscribe/unsubscribe), the resource (many subscribers of an audience), and the two targeting modes (subscriber ids or a matching filter). It is clear enough to distinguish from single-subscriber tools, but it does not explicitly differentiate itself from nearby bulk-removal or bulk-unsubscribe siblings.

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?

It implies the tool is for bulk audience subscription changes and gives the two targeting modes, including an example of filtering unengaged subscribers. However, it does not say when to prefer this over siblings like bulk-remove-audience-subscribers or bulk-unsubscribe-contacts, nor does it state exclusions or prerequisites.

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