Add subscriber to form

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

The annotations (destructiveHint=true, idempotentHint=false, openWorldHint=true) already flag the mutation risk, but the description adds useful specifics beyond them: it names the affected domains (delivery, audience membership, published data) and irreversible state, and states the confirm=true requirement. This is richer than the annotations alone.

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?

Two short sentences, front-loaded with the core action and followed by the risk/confirm caveat. No filler, nothing that doesn't earn its place.

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, non-idempotent mutation with no output schema, the description covers the side effects and the required confirm flag, which is the key operational detail. It could still say more about what the operation returns or how it interacts with the sibling form-add tools, but it is largely complete.

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 86%, so the schema already documents form_id, subscriber_id, account, confirm, payload, etc. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 clear verb+resource ('Add subscriber to form') that an agent can act on. However, it does not distinguish this from the close sibling add_subscriber_to_form (the email-based variant) or bulk_add_subscribers_to_forms, so the agent must guess which form-add variant to pick.

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?

The description gives the confirm=true prerequisite but no guidance on when to use this tool versus add_subscriber_to_form, add_subscriber_to_sequence_by_id, or the bulk variant. No when/when-not or alternative routing is offered.

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