get_order_details

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

No annotations are provided, so the description carries the full burden. The verb 'Fetch' implies a read-only operation, and the listed fields give some context about the response content. However, it does not disclose potential errors, permission requirements, or any conditions under which the operation might fail, leaving behavioral aspects only partially transparent.

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, unambiguous sentence that front-loads the action ('Fetch full order details') and immediately provides the key fields expected. No unnecessary words or fluff.

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 fetch tool with one parameter and no output schema, the description adequately specifies what will be returned (line items, prices, shipping, payment status). It lacks any mention of error handling or edge cases, but given the tool's simplicity, it is nearly complete.

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 a complete description of orderId as 'Order ID or order number' with types specified, achieving 100% coverage. The description adds no additional meaning beyond the schema, so per the baseline for high coverage, it scores a 3.

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 'Fetch full order details' with a clear verb and resource, and lists specific fields (line items, prices, shipping address, payment status). This distinguishes it from sibling tools like get_product_details or list_merchant_orders, making its purpose unambiguous.

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 full order details are needed, but it does not explicitly state when to use this tool versus alternatives like list_merchant_orders or track_customer_order. It lacks exclusion criteria or mention of alternative tools, so guidance is only implicit.

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