shopify_get_order

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

No annotations are supplied, so the description must carry the burden of behavioral disclosure. 'Get' weakly implies a read-only operation, but the description does not mention error behavior, response contents, or any side effects.

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?

One focused sentence with no filler, and the core action plus identifier mode are front-loaded. This is appropriately concise for a one-parameter read tool.

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?

Although the tool is simple, the absence of annotations and output schema leaves the agent without information about return shape or failure modes. There is also no mention of the more general order-listing tool for comparison, so the description is only minimally 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 description offers only 'by ID,' adding little beyond the schema's property name orderId. With 0% schema description coverage, the description should explain what kind of identifier this is or how it should be formatted, but it does not.

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 ('Get') and resource ('an order'), with 'by ID' clarifying that this is a single-record fetch rather than a list operation. This distinguishes it from sibling shopify_list_orders while following the same naming convention as other getters.

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?

There is no guidance on when to use this tool versus the sibling list_orders or whether additional prerequisites exist. An agent must infer that this is appropriate when an order ID is already known.

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