list_audiences

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

There are no annotations, so the description carries the full burden; it states the operation is a list/read, but does not disclose pagination behavior, rate limits, or that 'all' is constrained by the `count` parameter. The description does not contradict any annotations (since none exist).

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 sentence of six words, front-loading the action and object. It contains no filler or redundant phrases.

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 tool with two optional parameters, the description is sufficient but minimal. It does not mention that results are paginated or describe the return shape, but the schema covers the pagination parameters and the name implies the return type. Given the low complexity, it is complete enough.

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 provides complete descriptions for both `count` and `offset`, so the description does not need to explain them. The description does not add any additional parameter semantics beyond the schema.

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 the specific verb 'List' with the direct object 'Mailchimp audiences' and clarifies with '(lists)' to disambiguate from other audience-related tools. It clearly contrasts with the singular `get_audience` sibling by indicating this returns all audiences.

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 explicit guidance is provided about when to use this tool vs alternatives like `get_audience`. The usage is implied by the word 'all', suggesting this is for retrieving multiple audiences, but the description does not explicitly exclude or recommend alternatives.

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