mailchimp_audiences

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

With no annotations, the description carries the behavioral disclosure burden. It clearly indicates a read-only listing operation and reveals the key output (counts and stats), but it does not disclose pagination, authentication requirements, rate limits, or any behavior around the 'format' parameter. This is a basic but not rich level of transparency.

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, tightly worded sentence with no filler. The main action and resource are front-loaded, and the added detail about subscriber counts and stats earns its place.

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 simple list operation with one optional parameter and a present output schema, the description covers the core behavior. However, it leaves the 'format' parameter unexplained and offers no guidance on access or limitations, so an agent is not fully equipped to invoke the tool in non-default ways.

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 only parameter 'format' has no schema description, and schema description coverage is 0%. The tool description does not mention this parameter at all, leaving an agent to guess what values are accepted or how the parameter affects the output. The description fails to compensate for the lack of schema-level documentation.

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') with a clear resource ('Mailchimp audiences') and specifies what is returned ('subscriber counts and stats'). It is immediately distinguishable from sibling tools like mailchimp_campaigns because the resource is explicit.

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?

No guidance is provided about when to use this tool versus alternatives. The description simply states what it does; there is no mention of prerequisites, exclusions, or why an agent would choose this over a sibling like mailchimp_campaigns.

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