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

Annotations already declare this a non-read-only, destructive, open-world write, and the description adds value beyond them: the 100-item cap, the upsert behavior (existing email is updated rather than duplicated), and the outbound side effect of confirmation emails depending on list settings. It does not explain partial-failure behavior or whether an update overwrites existing field values — the latter is in mild tension with idempotentHint=false but is not a contradiction.

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 compact sentences with the risk warning front-loaded in caps, followed by capability, side effect, and compliance note — each sentence carries distinct information with no repetition.

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 bulk mutation tool with no output schema, the description covers scope, upsert semantics, side effects, and consent. The main gap is what happens when some of the 100 entries are invalid — whether the batch partially succeeds — which an agent cannot infer from annotations alone.

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 50%: custom_fields is documented inline and the '1 to 100 subscribers' description is present, but list_uid carries no explanatory text in the schema. The description implies list_uid identifies the target list and restates the 100 cap, but adds no format or lookup hints (e.g., that list UIDs come from mailblaze_list_lists), so it only partially compensates.

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 (add subscribers to a mailing list), adds the distinguishing scope ('bulk', up to 100 in one request) and the upsert rule that separates it from mailblaze_add_subscriber. An agent can tell exactly what this does and how it differs from the single-subscriber sibling without opening the schema.

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?

'Only add people who agreed to receive your email' is a real precondition, and 'may send confirmation emails' sets expectations before calling. But there is no explicit routing guidance against siblings (single add, update_subscriber, or checking with find_subscriber_by_email first), so when-to-use is only implied by the bulk framing.

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