mailchimp_ecommerce_orders_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 behavioral disclosure. It implies a read-only operation through 'Get' but provides no details on response format, error behavior, or rate limits. It is minimally transparent but lacks richness for a tool that could benefit from describing what information is returned.

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 with no redundant words. It is efficient and appropriately sized for a simple retrieval tool, earning a perfect score for conciseness.

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 two-parameter get tool, the description is minimally adequate but leaves notable gaps: it does not state what information is returned, that the order is scoped to a store, or how it differs from list/get siblings. The absence of an output schema increases the need for a richer description, resulting in a score of 3.

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 already provides 100% coverage for both store_id and order_id with clear descriptions. The description adds no additional meaning beyond the schema, so the baseline 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 clearly states the action ('Get') and the target ('a specific order'), which distinguishes it from list (all orders) and mutation tools. However, it doesn't explicitly mention that it is scoped to an ecommerce store or that both store_id and order_id are required, relying on the tool name and schema to convey this.

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 like mailchimp_ecommerce_orders_list or mailchimp_ecommerce_orders_get. It doesn't mention prerequisites, context, or any exclusions, leaving the agent without clear selection criteria.

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