shopify_get_inventory_levels

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It communicates a read operation through 'get' but does not mention pagination behavior, whether at least one ID filter is required, how limits apply, or whether calling with no IDs returns all inventory levels. These are material gaps for an agent deciding how to invoke the tool.

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 concise front-loaded sentence with no filler. It conveys the core action and the main filtering dimensions efficiently, though it could have used the brevity to add a key parameter detail without becoming verbose.

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?

With no annotations, no output schema, and zero schema description coverage, the one-line description leaves the agent without essential context such as the meaning of the limit parameter, the format of ID strings, and whether either ID filter is required. It is minimally sufficient to guess the tool's purpose but not complete enough for confident correct invocation in all cases.

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 parameter documentation gap. It does clarify that inventory_item_ids and location_ids are filters, but it does not explain the expected string format (e.g., comma-separated IDs) and completely omits the limit parameter. Thus the description only partially compensates for the missing schema descriptions.

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 contains a specific verb ('Get'), a clear resource ('inventory levels'), and the key filtering dimensions ('by item or location IDs'). It is immediately distinguishable from all sibling tools, none of which target inventory levels.

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 this tool is for retrieving inventory levels when item or location IDs are relevant, and no sibling offers the same capability. However, it does not explicitly state when to use this tool over alternatives or when not to use it, leaving some inference required.

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