mailchimp_ecommerce_stores_list

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'Get all e-commerce stores' without explaining pagination behavior, ordering, default count limits, or any required account setup. The read-only nature is only implied by 'Get'.

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 concise sentence that front-loads the action and resource. Every word contributes to the meaning, with no filler or redundant information.

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 two optional pagination parameters, the description provides the core purpose. However, it does not mention response format or default pagination limits, which could be important given the absence of an output schema. Still, the tool is relatively simple, so this is minimally adequate.

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 coverage is 100% because both count and offset have descriptions ('Number of records to return' and 'Number of records to skip'). The tool description adds no additional meaning beyond the schema, making the baseline 3 appropriate.

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 retrieves all e-commerce stores connected to the account, using the verb 'Get' and specific resource 'e-commerce stores'. This distinguishes it from sibling tools like ecommerce_stores_get (single store) and ecommerce_stores_add/update/delete (mutations).

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 phrase 'Get all' implies this tool is for listing multiple stores, contrasting with tools that fetch a single store or modify stores. However, it does not explicitly mention when to use this instead of other list tools (e.g., products_list, orders_list) or provide exclusions.

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