mailchimp_members

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

With no annotations provided, the description carries the full transparency burden. It discloses ordering (newest-first), pagination via count/offset, activity limits (last 50), and note_id dependency. These are meaningful behavioral traits beyond the schema, though it doesn't explicitly state read-only or cover auth/rate limits.

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 dense but efficiently structured with semicolons to separate actions. There is no redundant filler, but the single long sentence could be slightly easier to scan if broken into bullets. Overall, it 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?

The description comprehensively covers all action variants, parameter dependencies, and behavioral details like pagination and activity limits. Without an output schema, it provides enough context to select and invoke the tool correctly, leaving little ambiguity.

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?

Although the schema covers 100% of the parameters, the description adds value by explaining what each action returns (e.g., 'details' includes merge fields, interests, stats), clarifying that 'note' requires note_id, and describing pagination behavior for 'list'. This raises it above the baseline.

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 domain—Mailchimp members and their associated data—and lists nine distinct retrieval actions, distinguishing it from sibling tools. However, the opening is a noun phrase ('Subscribers in one audience') rather than an explicit verb phrase, which slightly weakens the clarity.

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 this tool and breaks down each action into its specific use case (list, details, tags, activity, etc.). It does not explicitly mention alternatives or exclusions, but the detailed action list effectively guides selection.

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