shopify_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 does not disclose that authentication parameters (api_key, access_token) are needed, nor does it mention pagination, default ordering, or the scope of orders returned. The description is too vague to inform the agent about 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 a single sentence, which is concise but at the expense of crucial details. It front-loads the purpose, but lacks specificity, making it minimally adequate. The sentence earns its place by stating the basic function, but could be expanded without losing conciseness.

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's complexity (6 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain the return format, authentication process, or how filters work. The agent cannot reliably determine correct usage without additional information.

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 description coverage is 0%, and the description does not add meaning beyond parameter names. While 'limit', 'status', and 'financial_status' are somewhat self-explanatory, the description fails to clarify allowed values or the role of 'api_key' and 'access_token'. The description should compensate for missing schema details.

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 'Get orders from a Shopify store,' specifying the verb 'get' and the resource 'orders from a Shopify store.' This distinguishes it from sibling tools like shopify_products or shopify_customers, though it could mention the optional filters (limit, status, financial_status) for more precision.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no examples of appropriate contexts. Sibling tools like shopify_fulfillments or shopify_inventory might be confused without additional context.

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