get_customer_order

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

With no annotations provided, the description itself conveys the tool's read-only nature via 'Get' and additionally discloses a behavioral trait: 'with expanded positions' indicates the response includes nested position data. It does not mention error behavior or permissions, but for a simple lookup this is reasonable transparency.

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, front-loaded with the action and resource. Every word contributes meaning, with no fluff or redundancy.

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 single-resource lookup with one parameter and no output schema, the description covers the essential purpose and the notable behavior of expanded positions. It does not describe response format or error handling, but these are less critical given the tool's simplicity.

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 documents the only parameter 'id' as 'Customer order UUID' with 100% coverage. The description's 'by UUID' restates the schema without adding new syntax, format details, or parameter semantics, so the description adds no meaningful value beyond the structured field.

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 uses a specific verb 'Get' and resource 'customer order', scoped to a single UUID, and mentions 'expanded positions' to indicate the response richness. This clearly distinguishes it from sibling list tools like get_orders or mutation tools like create_customer_order.

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 implies usage when a specific order UUID is known and the caller needs the order with its positions. However, it does not explicitly state when to prefer this over get_orders or any alternative, nor does it mention prerequisites beyond having a UUID. Guidance is implied but not explicit.

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