mailchimp_ecommerce_customers_get

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'Get information', which is a minimal restatement of the tool name and does not explain anything about response format, error handling, permissions, or potential side effects. Since no annotations exist, the lack of additional behavioral context is a significant gap.

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 immediately states the action and resource. There is no wasted verbiage or redundant information. It is appropriately sized for a simple get operation and front-loaded with the core purpose.

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 read operation with two well-described parameters, a minimal description might be sufficient, but the absence of any mention of return structure, store context, or behavioral caveats leaves some ambiguity. The description lacks the rich contextual details that would make it fully self-sufficient, especially given the absence of annotations and output schema.

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 covers 100% of parameters and provides descriptions for store_id and customer_id. The tool description does not add any further meaning beyond what the schema already offers. Given the high schema description coverage, the baseline score of 3 is 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 states a specific action ('Get') and resource ('customer'), and qualifies it as 'a specific customer', which distinguishes it from sibling tools like list operations. However, it does not explicitly contrast itself with other get operations or mention the store context, so it falls just short of fully differentiating from all siblings.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention when to choose it over mailchimp_ecommerce_customers_list or the add/update/delete counterparts, nor does it state any prerequisites or edge cases. The intended usage is only implied by the tool name and parameters.

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