shopify_list_fulfillment_orders

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

No annotations are provided, so the description carries full burden. It discloses that the tool lists fulfillment orders and includes locations and tracking, but does not mention pagination, rate limits, error handling, or the fact that it is a read-only operation. Additionally, the description states order_id is required, while the schema makes it optional (anyOf string/null, default null), creating a contradiction that undermines transparency.

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 concise with two sentences plus an Args section. It front-loads the core purpose and parameter, with no redundant information.

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?

Given the tool has an output schema, return values need not be explained. However, the description lacks usage guidance and the required/optional inconsistency is a gap. For a simple list tool, it is adequate but not 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 adds meaning by explaining that order_id is the Shopify order ID and can be numeric or GID. However, schema description coverage is 0%, and the description incorrectly marks it as required when schema allows null. No examples or format details are provided.

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 it lists fulfillment orders for a Shopify order, including locations and tracking. The verb 'list' and resource 'fulfillment orders' are specific. However, it does not explicitly differentiate from sibling tools like shopify_list_transactions or shopify_list_refunds, relying on the tool name for distinction.

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 mentions that order_id is required but provides no guidance on when to use this tool versus alternatives. It lacks prerequisites, exclusions, or context for selecting this tool over other list tools for Shopify.

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