mailchimp_ecommerce_customers_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention pagination behavior despite the count and offset parameters, nor does it clarify that 'all customers' may actually be a paginated list. It also lacks any notes about authentication, rate limits, or the shape of the response.

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, focused sentence that immediately communicates the core purpose. No unnecessary words 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 4 parameters and no output schema, the description is too sparse. It fails to mention pagination, filtering via email_address, or the fact that store_id is required (though the schema indicates this). The agent may not correctly understand how to retrieve all customers or whether the result is a single page or complete list.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain how count/offset affect the list or how email_address filters results. It only reinforces store_id implicitly.

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 'Get all customers for a store' clearly states the action (get), the resource (customers), and the scope (for a specific store). It distinguishes from sibling tools like mailchimp_ecommerce_customers_get, which implies fetching a single customer, and from add/update/delete operations.

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 no guidance on when to use this tool versus alternatives. It does not mention that for a single customer you would use mailchimp_ecommerce_customers_get, or that modifications use add/update/delete. The usage is only implied by the tool name and context.

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