Bulk add subscribers to forms

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

Annotations already flag destructiveHint=true and non-idempotency, so the safety profile is partly covered. The description adds genuine value beyond that: it names what is affected (delivery, audience membership, published data, irreversible state) and discloses an auth requirement (OAuth only, no API keys) that the annotations do not carry.

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, all earning their place: intent, impact, and hard invocation requirements. The destructive/confirm constraint is front-loaded where it matters most.

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 bulk mutation with no output schema, the description supplies the critical missing context: blast radius, confirm gating, and auth constraints. It is only slightly short on the bulk-vs-single routing an agent needs to pick this over its singular siblings.

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 coverage is 67% and the nested payload/additions/payload_file exclusivity is documented in the schema itself. The description only echoes confirm=true, adding no meaning beyond the schema on account, callback_url, or the mutually exclusive body forms. Baseline 3 is appropriate when the schema does most of the work.

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?

Names a specific verb and resource ("bulk add subscribers to forms"), and the "bulk" qualifier implicitly separates it from the singular siblings add_subscriber_to_form / add_subscriber_to_form_by_id. However, it never explicitly states the single-vs-multiple distinction, leaving the agent to infer which sibling applies.

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?

Gives concrete invocation constraints (requires confirm=true, requires OAuth, API keys unsupported), which is real usage context. But it offers no when-to-use-vs-alternatives guidance relative to the single-subscriber sibling tools, nor any when-not condition.

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