Bulk create subscribers

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the mutation risk is flagged structurally. The description goes beyond them by naming the affected surfaces (delivery, audience membership, published data, irreversible state) and adding the auth constraint that API keys are not supported, which annotations do not cover.

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?

Four short sentences, front-loaded with the action and immediately followed by risk, confirmation, and auth requirements. Minimal waste; the only redundancy is restating the tool title in the first 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 bulk mutation with nested subscriber objects and no output schema, the description omits batch-size limits, partial-failure behavior, and whether duplicate email_addresses are merged or rejected — all material to calling a bulk endpoint correctly. Risk and auth are covered, but bulk mechanics are not.

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% and the schema itself documents account, confirm, payload, payload_file, and the subscriber fields, so most parameter meaning is already conveyed. The description's only added semantic is that confirm is required here (the schema leaves required empty), which is genuinely useful but thin against six parameters.

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 ('Bulk create subscribers'), and the 'Bulk' qualifier distinguishes it from the singular create_subscriber sibling at the name level. However, the description body never explicitly contrasts itself with create_subscriber, bulk_add_subscribers_to_forms, or the payload/body-flag variants, so routing relies mostly on the tool name.

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 supplies real preconditions — confirm=true is mandatory and OAuth is required (API keys unsupported) — which tells the agent when the tool can be invoked at all. It gives no guidance on when to prefer this over create_subscriber or bulk_add_subscribers_to_forms, so alternative selection is left to inference.

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