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

No annotations are provided, so the description carries the full behavioral burden. It does disclose return content (the raw GraphQL fields, including a resolved material) and clarifies the id semantics, which is genuine added value absent an output schema. It stops short of disclosing auth/permission needs, rate limits, or behavior when the order or shop id is invalid, so the burden is only partly met.

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?

Two compact sentences with the payload description front-loaded and the identifier guidance second. The field list is dense but scannable; the only mild cost is that it reads as a comma-stuffed inventory rather than a structured list.

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 read-only fetch with no output schema, listing the returned attributes is exactly the right compensation, and identifier semantics are covered. Missing is whether the result is a collection, how large orders are paginated, and what happens on a not-found order, which are the remaining gaps for an agent to call it confidently.

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 the baseline is 3, but the description goes beyond by giving a concrete order-number example (BU741087) that demonstrates the accepted format, and it explicitly ties shopId to the ApiCredential.Id concept. It leaves intentId (from RecordUserQuestion) entirely unexplained in the prose, which keeps it from a 5.

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?

States a specific verb (Fetch) and a precise resource (raw Shopify GraphQL line items for an order), then enumerates the returned attributes (product, variant, SKU, customAttributes, product-linked flag, resolved material). This clearly separates it from siblings like GetLabelsForOrder, FetchWebshopOrder, and FindOrder without opening either schema.

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?

Gives usable invocation guidance (supply shopId as ApiCredential.Id, accept either an order number like BU741087 or an external Shopify order id), which is implied 'how'. However, it never states when to prefer this tool over alternatives such as FetchWebshopOrder or OrderInvestigation, and offers no exclusions or preconditions.

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