mailchimp_campaigns_list

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'List all campaigns' which implies a read operation, but gives no details about pagination, response shape, default sorting, or any side effects. The addition of 'optional filters' is minimal and does not enrich the agent's understanding beyond the tool name.

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?

A single, clear sentence that immediately states the action and scope. No filler words or redundant details. Perfectly front-loaded and concise.

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 list tool with 8 parameters and no output schema, the description is minimally adequate. It clearly identifies the operation but does not describe what the returned data contains (e.g., campaign summaries, pagination info) or any constraints beyond the schema. Given the lack of annotations and output schema, the description is not fully complete but is not severely deficient.

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 schema description coverage is 100%, so all 8 parameters are already documented with descriptions. The description's 'optional filters' is a generic phrase that does not add specific parameter insights. With full schema coverage, baseline 3 is appropriate.

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 ('List') and resource ('campaigns') with clear scope ('all campaigns in your Mailchimp account'). This distinguishes it from sibling tools like 'get' (single campaign) and 'search_campaigns' (search functionality).

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 no guidance on when to use this tool versus alternatives. It does not mention when to use mailchimp_campaigns_get for a single campaign or mailchimp_search_campaigns for search. No prerequisites or exclusions are stated.

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