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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that this is a single-resource GET scoped to a customer/subscription pair and lists the returned attributes, but says nothing about auth requirements, rate limits, or error behavior for a missing origin order.

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 short sentences, front-loaded with the resource definition followed by the endpoint. No filler and nothing an agent must wade through.

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 read-only two-parameter lookup with no output schema, the description gives enough: what the resource is and the three fields returned. Only the absence of failure-mode context (what happens if no origin order exists) keeps it from a 5.

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 both parameters are already documented in detail (including the gid:// acceptance). The description only adds the REST path template showing where each id plugs in, which is minor value beyond the schema.

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 the specific resource (the Shopify order that started a subscription) and enumerates what comes back (id, name, creation date), which meaningfully separates it from the sibling awtomic_get_origin_order_fulfillments. It doesn't explicitly name that sibling or otherwise tell the agent how it differs from awtomic_get_subscription, so it falls short of full sibling differentiation.

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?

Usage is only implied: an agent can infer this is the call to make when it needs the original order behind a subscription contract. There is no statement of when to prefer this over awtomic_get_origin_order_fulfillments or awtomic_get_subscription, and no prerequisites are given.

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