get_product

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

With no annotations present, the description fully carries the burden of explaining behavior. It clearly indicates this is a read operation ('Read one product in full'), describes the extent of data returned (variants with SKU, price, stock level), and does not imply any side effects.

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 concise and well-structured, using two sentences to convey the tool's purpose, the data returned, and the parameter constraint. No unnecessary words or redundancy.

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 simple fetch operation without an output schema, the description provides sufficient context: what it does, what data is included, and how to specify the target. It does not leave critical gaps that would prevent correct usage.

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 description adds meaningful constraints beyond the schema by stating that exactly one of the two parameters (id or handle) must be used. This clarifies the relationship and use of the parameters, which the schema alone does not fully convey.

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 the tool reads a single product in full, including variants with SKU, price, and stock level. It distinguishes itself from siblings like search_products and check_inventory by focusing on retrieving a specific product's complete data.

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?

It explicitly instructs that the product must be identified by handle or by gid://shopify/Product/... id and that exactly one of the two must be provided. This gives clear guidance on when to use this tool versus alternatives.

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