get_product_inventory

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'shows' inventory, which implies a read operation, but it does not disclose whether inventory is aggregated across locations, whether out-of-stock variants are included, or what the response structure looks like. This leaves significant behavioral ambiguity.

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, front-loaded sentence that directly states the tool's core function with no extraneous words. It is concise, well-structured, and every word earns its place.

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 one-parameter tool, the description covers the basic purpose but lacks critical context such as the exact return format (e.g., list of variants with quantities) and how it differs from related inventory tools like get_inventory_levels. Since there is no output schema, the description should provide more explicit details about what the agent can expect.

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 single parameter productId is fully documented in the schema with a clear description ('Shopify Product GID') and type, giving 100% schema coverage. The tool description adds no additional parameter-level detail, so the baseline of 3 applies without extra value from the description.

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 the specific verb 'shows' with a clear resource ('full inventory of a product') and scope ('all variants'), making the tool's primary function unambiguous. However, it does not explicitly differentiate from sibling tools like get_inventory_levels, which could also be interpreted as inventory-related, so it stops short of full distinction.

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?

There is no guidance on when to use this tool versus alternatives such as get_inventory_levels or get_product. The description states what the tool does but does not provide context on preferable use cases, conditions, or exclusions, leaving the agent without directional help.

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