shopify_get_product

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

Annotations already establish the tool as read-only, open-world, idempotent, and non-destructive. The description adds a meaningful behavioral caveat that is not derivable from the schema or annotations: returned cursors must be followed independently.

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 short sentences with no filler; the core purpose is front-loaded and the pagination caveat is a distinct, valuable addition. Every sentence earns its place, even though the brevity contributes to incompleteness penalized elsewhere.

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 tool with five parameters, no output schema, and no schema-level parameter descriptions, this is too sparse. The roles of store, id, and first are left implicit, and the exact relationship between after/mediaAfter and variants/media is not fully clarified. The cursor note helps but does not make the definition complete enough for an agent to call it correctly on first try.

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%, so the description must compensate for the five parameters. It only hints that after and mediaAfter relate to cursors via the mention of variants/media and 'returned cursor'; it does not explain store, id, first, or the precise difference between the two cursor parameters.

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 an active verb with a specific resource and names the key returned content: product details, variants, and media. It is clearly distinguished from search/list siblings in intent, though it does not explicitly carve out boundaries against close siblings like shopify_get_product_everywhere or shopify_search_products.

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?

No guidance is given on when to prefer this tool over alternatives such as shopify_search_products, shopify_get_product_everywhere, or shopify_find_sample_product. The only procedural instruction is about cursor pagination, not about tool selection or context.

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