Query Multiple Shopify Stores

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful behavioral context beyond annotations: parallel execution and per-store success/error isolation. It does not discuss rate limits or aggregation details, but the core execution behavior is disclosed.

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?

Two sentences with no filler. The core operation, scope, execution mode, and result model are all conveyed efficiently, with the most important constraints front-loaded.

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 network-fan-out tool with full schema coverage, helpful annotations, and no output schema, the description covers the essential details: read-only query, multiple stores, parallel execution, and per-store result isolation. It could be slightly richer on the exact return shape, but it is sufficient for an agent to invoke the tool correctly.

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% for all three parameters, so the schema already documents query, stores, and variables. The description reinforces the 'same query across stores' relationship but does not add new parameter-level meaning beyond what the schema provides, matching the baseline for full coverage.

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 a specific verb ('Run'), the resource ('the same read-only GraphQL Admin API query'), and the differentiating scope ('across multiple named stores in parallel'). This distinguishes it from sibling tools like shopify_graphql_query without needing to open the schema.

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 identifies the intended use case: running one read-only query across several stores. It does not explicitly name alternatives or state when not to use this tool, but the parallel multi-store scope is clear enough to guide selection.

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