mailchimp_automations

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

With no annotations provided, the description carries the full burden of disclosure. It details what each action returns, such as 'full automation record including its report_summary' and 'emails in the automation, in send order'. It also mentions the limitation that 'Customer journeys are not exposed'. It does not explicitly state that the tool is read-only, but the action names imply it. The behavioral expectations are adequately communicated.

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 a single dense paragraph, but every sentence contributes useful information. It front-loads the core purpose and then enumerates actions with their purpose and parameter needs. It could be slightly more structured (e.g., bullet-style), but it is not verbose or redundant.

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 the tool's complexity (7 actions, 6 parameters) and absence of output schema/annotations, the description covers the essential mapping of actions to their results and input dependencies. It explains the starting action (list) and what each subsequent action returns. It does not detail exact return structures or edge cases, but for a list/data-retrieval tool this is sufficient.

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 coverage is 100%, so the baseline is 3. The description adds value by tying action values to required parameters, e.g. 'queue_subscriber (one queued subscriber, needs email_id and subscriber_hash)' and 'list (all automations — start here for a workflow_id)'. This clarifies the workflow and dependency between parameters beyond the schema's individual descriptions.

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 identifies the tool's resource as 'Classic automations, their emails, and subscriber queues' and enumerates seven specific actions (list, details, emails, etc.) that define its operations. It also distinguishes itself by stating 'Customer journeys are not exposed by the Mailchimp API', which clarifies boundaries relative to other potential automation-related tools.

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?

It provides action-level guidance, e.g. 'list (all automations — start here for a workflow_id)', and notes dependencies between actions (e.g. email_id from emails, workflow_id from list). It also offers a negative guideline by excluding customer journeys. However, it does not explicitly compare against sibling tools like mailchimp_campaigns, but the domain separation is implied.

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