Add subscriber to form by email address

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

Annotations already declare destructiveHint=true and non-idempotent, and the description reinforces this with 'May affect delivery, audience membership, published data or irreversible state.' It goes further than the annotations by flagging the confirm requirement and the irreversible nature, though it doesn't say what specifically becomes irreversible or how failures behave.

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, front-loaded with the action and followed by the risk and the precondition. No filler, though 'May affect delivery, audience membership, published data or irreversible state' is a somewhat generic risk menu rather than a precise statement.

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 mutation tool with nested payload/payload_file options, no output schema and destructive semantics, the description says enough to avoid misuse (confirm, irreversible effects) but leaves the parameter-selection story and return behavior entirely to the schema. Adequate, not 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 71% and the schema documents account, confirm, payload, payload_file and form_id itself. The description adds nothing about these parameters, only echoing the email-address field from the payload. Baseline 3 is appropriate when the schema carries most of the load.

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 and resource ('Add subscriber to form') and qualifies it with 'by email address', which distinguishes it from the sibling add_subscriber_to_form_by_id. However, it never explicitly names that sibling or bulk_add_subscribers_to_forms, so the differentiation is left to inference rather than stated.

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 only usage condition given is 'Requires confirm=true', which is a real prerequisite. There is no guidance on when to prefer this tool over add_subscriber_to_form_by_id or bulk_add_subscribers_to_forms, so the agent must infer the selection rule from the name alone.

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