Create Shopify Portfolio Snapshot

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces this with 'read-only'. It adds valuable context that results depend on scopes ('when scopes permit'), and that it includes specific counts. This exceeds the annotation baseline without contradiction.

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 well-structured sentences with the core purpose front-loaded and the scope condition clearly stated. No redundant information or filler.

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 low complexity (one optional parameter, no output schema), the description adequately explains what the snapshot includes and the scope dependency. It does not detail error conditions or exact response format, but covers the essential content for an agent to call it 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?

The schema provides complete documentation for the single 'stores' parameter, including format and omission behavior. The description merely restates this ('selected stores or every configured store') without adding new semantics beyond the schema's coverage, so 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 clearly states a specific verb ('Create') and resource ('read-only operating snapshot') and differentiates it from siblings by focusing on portfolio-level aggregation across multiple stores, which is distinct from single-store or query-based tools.

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 implies usage for portfolio-level snapshots ('across selected stores or every configured store') but does not explicitly state when to prefer this over alternatives like shopify_get_shop_info or shopify_graphql_query. The context is implied rather than explicit.

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