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

The description adds the behavior of the 'pending' status triggering a double-opt-in email, which is beyond the destructiveHint annotation. This provides useful context about side effects. However, it does not disclose duplicate-member handling or permission requirements.

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?

The description is two sentences, front-loading the main purpose ('Add a new member to an audience') and including only a behavioral note and REST endpoint. Every sentence contributes value.

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?

Despite the destructiveHint annotation, the description doesn't mention what happens on success, return values, or handling of existing members. Given no output schema and nested parameters, the description is somewhat thin for a mutation tool, but full schema coverage and a simple operation keep it adequate.

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?

The input schema already provides 100% parameter descriptions, so the baseline is 3. The tool description adds no additional parameter semantics beyond what's in the schema; even the pending status note is duplicated in the schema's status field description.

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 uses a specific verb ('Add') with a clear resource ('new member (subscriber)') and target ('audience (list)'), distinguishing it from sibling tools like mailchimp_update_member and mailchimp_archive_member.

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 clearly establishes the tool's context (adding a new member) but does not explicitly name alternatives or exclusions. The 'new' keyword implicitly differentiates from update/archive, but there's no direct 'when not to use' guidance.

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