get_store_order

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

Annotations already mark it as readOnly (safe read). Description adds return content details (lines, customer, totals) and specific fields. No contradictions. Good context beyond annotations.

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?

Concise and front-loaded: first sentence states purpose. Two short paragraphs plus Args/Returns. Every sentence adds value, no 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?

Covers return fields, usage context, and parameter sources. Missing mention of optional 'account' parameter. Output schema exists, so return structure detail is not needed. Adequate for complexity.

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 description coverage is 0%. Description compensates by explaining how to obtain store_id and order_id from other tools. The optional 'account' parameter is not mentioned, but required params are well-documented.

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 'Retrieve a single e-commerce order' with a specific verb and resource. It distinguishes from siblings like list_store_orders (listing) and create_store_order (creation) by specifying 'single' and indicating use after listing.

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?

Explicitly states when to use: 'to inspect one order's full detail after finding it via list_store_orders or list_account_orders.' Provides context on store types. Lacks explicit 'do not use' but is clear enough.

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