Find Low Stock Across Shopify Stores

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the agent knows this is a safe read-only operation. The description adds the behavioral detail of how the result is categorized (low, zero, negative), which is not in the annotations or schema. It doesn't overpromise or contradict annotations. However, it doesn't disclose whether the threshold applies per-variant or aggregate across stores, or how 'active' is defined, but that's a minor gap. Given the annotations cover the safety profile, a 4 is warranted for the added categorization context.

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, well-structured sentence that front-loads the core purpose ('find every active product variant at or below an inventory threshold') and adds a critical separator detail at the end. Every word contributes; no filler or redundant phrases. It respects the front-loading principle.

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 reporting tool with annotations that declare safety and idempotency, the description covers the core scope and result categorization. The schema handles all parameter definitions, so the description doesn't need to repeat them. The only missing piece is what the output looks like (e.g., which fields are returned), but with no output schema and the description's categorization promise, it's reasonably complete. A 4 is justified because it's clear enough for an agent to select and invoke, though an explicit return format hint would make it 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 description coverage is 100% - both 'stores' and 'threshold' have detailed descriptions in the schema itself. The description adds context that the tool uses these to filter and categorize, but it doesn't provide syntax or format details beyond the schema. The schema already explains that 'stores' is aliases and 'threshold' is the max quantity, so the description adds minimal extra value. Baseline 3 is appropriate.

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 uses a specific verb ('find'), a precise resource ('active product variant'), and a clear condition ('at or below an inventory threshold'). It separates the result into low, zero, and negative inventory, which adds nuance that distinguishes it from generic inventory tools. Though it shares the 'report' suffix with siblings like shopify_duplicate_sku_report, the scope (inventory threshold across stores) is unique.

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 clearly indicates the purpose (inventory management) and the operator model (selected stores via 'stores' parameter). It does not explicitly name alternatives or state when not to use this tool, but the scope over multiple stores and the threshold concept make the usage context clear. Since there are sibling tools like shopify_compare_inventory and shopify_catalog_health, a brief mention of those would have made it a 5, but it's mostly clear.

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