Mailchimp MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the campaign is sent 'immediately' and has prerequisites, but it does not cover critical aspects like whether this action is reversible, what permissions are required, potential rate limits, or what happens after sending (e.g., status changes). This leaves significant gaps for a mutation tool.

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 very concise—two sentences that directly state the action and prerequisites without any fluff. It is front-loaded with the main purpose, making it efficient and easy to parse.

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?

Given that there is an output schema (which reduces the need to describe return values) but no annotations and low schema coverage, the description is moderately complete. It covers the basic action and prerequisites but lacks details on behavioral traits, error handling, or integration with sibling tools, which are important for a mutation operation in this context.

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 has 1 parameter with 0% description coverage, so the description must compensate. It implies the 'campaign_id' parameter is used to identify the campaign to send, but it does not add specific meaning beyond what the schema's title ('Campaign Id') suggests, such as format or sourcing details. This meets the baseline for minimal parameter info.

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 clearly states the action ('send a campaign immediately') and specifies the resource ('campaign'), which distinguishes it from sibling tools like 'schedule_campaign' or 'replicate_campaign'. However, it does not explicitly differentiate from all siblings, such as 'send_test_email', which might be a related but distinct operation.

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 provides some context by stating prerequisites ('campaign must be in 'save' status with content set'), which implies when to use this tool. However, it does not explicitly mention alternatives like 'schedule_campaign' for delayed sending or 'send_test_email' for testing, nor does it specify when not to use it, such as if the campaign is already sent.

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