get-product-by-id

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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb 'Get' implies a non-mutating read operation, and listing the returned categories adds some clarity. Still, it does not address error/not-found behavior, authorization needs, or response shape beyond the listed fields.

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 efficient sentence that front-loads the core purpose and immediately adds useful detail about the returned content. There is no filler or redundant restating of the tool name.

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 one-parameter read operation, the description plus schema covers the essential invocation needs: what the tool returns and how to specify the product. It is slightly incomplete because it omits not-found/error behavior and does not explicitly route users to get-products for listing, but the low complexity makes this a minor gap.

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 input schema already fully documents the single parameter, including both acceptable ID formats (numeric or gid://shopify/Product/...). Schema description coverage is 100%, so the description itself adds no parameter-level meaning. 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 ('Get') and resource ('single product') and identifies the included detail categories (description, images, variants). This distinguishes it from sibling list tools like get-products by signaling a targeted, single-item lookup.

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 tool name and 'single product' wording imply usage when a specific product ID is known, and get-products is the obvious sibling for listing. However, the description never explicitly states when to prefer this tool over get-products or what conditions make it the right choice.

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