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

The annotations already declare readOnlyHint=true, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context: it acts on 'the connected Shopify store' and returns a list of recent orders with the listed fields, which adds modest value beyond annotations.

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 main sentence is front-loaded and efficient, with useful details packed into one sentence and a clear usage hint. The 'Routing:' line is somewhat redundant with the first sentence but does not significantly hurt readability.

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 list operation with 100% parameter coverage and safety annotations, the description is reasonably complete: it describes the returned fields, optional filter support, and scope. There is no output schema, but the field list partially compensates for that.

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 100%, so the parameters are already well documented. The description confirms that `query provides Shopify order filtering, but does not add much meaning beyond what the schema already provides, matching the baseline.

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 and resource: 'List recent orders from the connected Shopify store' and enumerates the returned fields (order name/number, total, financial/fulfillment status, created date). It is clearly an order-list operation rather than a single-order lookup, though it does not explicitly name alternatives like get_shopify_order.

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?

It clearly says the tool is for seeing recent sales and their state, and mentions the optional Shopify `query` filter. It does not explicitly exclude alternatives or name siblings, but the context is sufficient for an agent to know when to call it.

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