mailchimp_orders

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

With no annotations provided, the description carries the burden of behavioral disclosure. It details what each action returns (list: orders with totals and attribution; details: full record with line items; lines: line items only) and notes dependencies like order_id. It does not explicitly state read-only behavior, but the action verbs imply it.

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 two sentences, front-loaded with the core purpose, and then provides a compact breakdown of actions. Every sentence is informative 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?

Given no output schema and no annotations, the description does a good job of conveying the tool's variants and dependencies. Pagination is not mentioned, but the schema covers count/offset. It is complete enough for an agent to select and invoke the correct action, though it could elaborate on the return shape.

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%, so the baseline is 3. The description adds meaningful semantics for the action parameter by elaborating what each enum value returns, and it clarifies the role of order_id as required for details/lines. This goes beyond the schema's terse descriptions.

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 this tool handles orders and line items for a single store, with a specific verb implied by the action options (list, details, lines). It distinguishes from sibling tools like mailchimp_stores or mailchimp_reports by focusing on order data and campaign attribution.

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 explains the three action modes and their prerequisites (details and lines require order_id), giving clear context on how to use the tool. It scopes usage to 'one store,' implying it is not for cross-store queries, but no explicit alternatives are named.

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