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

The description adds behavioral details beyond the readOnlyHint annotation by disclosing pagination, optional status filtering, and sorting. It also provides the REST endpoint, which gives insight into the underlying operation. However, it does not describe return formats or potential rate limits, which are not covered by annotations.

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, front-loaded sentence that names the purpose, then adds the key behaviors (paginated, optional status filter, sort) and the REST endpoint. Every word earns its place, with no redundancy or filler.

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 6 parameters and no output schema, the description covers the essential aspects: purpose, pagination, filtering, sorting, and the REST method. It does not explain return value structure or pagination specifics beyond what the schema provides, but given the schema's richness and annotations, it is adequately complete.

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 already provides 100% coverage of parameter descriptions, including defaults and enums. The description adds no new semantic meaning for parameters beyond mentioning 'optional status filter and sort', which is already stated in the schema. The REST endpoint is a minor addition but does not significantly enhance parameter understanding.

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 tool lists members of an audience, using a specific verb and resource. It distinguishes itself from siblings like mailchimp_get_member (single member) and mailchimp_search_members (search) by explicitly focusing on listing all members with pagination, status filter, and sort options.

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 clear context for when to use the tool: when you need to list members of a specific audience, with support for pagination, filtering by status, and sorting. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to differentiate it from sibling tools.

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