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

Annotations already establish that this is a read-only, open-world, non-destructive operation. The description adds useful behavioral context beyond annotations, including that numeric queries may match external order IDs or prefixed display numbers and that recipientName disambiguates ambiguous matches. It does not cover auth, rate limits, or error behavior.

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 front-loaded with the core action and is appropriately sized for a seven-parameter lookup tool. The sentences are dense but every sentence contributes relevant lookup or disambiguation context.

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 multi-platform read-only lookup with full schema coverage and existing safety annotations, the description is nearly complete. It covers the action, accepted identifiers, optional filters, and ambiguity handling, though it does not describe return shape or error behavior in the absence of an output schema.

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 parameter descriptions already carry the baseline burden. The description still adds meaning beyond the schema by explaining platform-specific order-number formats, when shopId narrows results, and how recipientName and organizationQuery help resolve unknown-shop cases.

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 a specific verb and resource: fetch an order from live Shopify, WooCommerce, or CCV Shop APIs by order number or external order ID. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as FindOrder or OrderInvestigation.

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 gives parameter-level usage guidance, such as using shopId to narrow a search and recipientName to disambiguate matches. However, it does not say when to use this tool instead of alternatives like FindOrder or OrderInvestigation, so tool-selection guidance is only implied.

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