shopify_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, yet it says nothing about authentication needs despite api_key, access_token and shop_domain parameters implying credential handling. Read-only semantics are only weakly implied by 'Get', and there is no mention of pagination, limits, or response shape.

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?

A single short sentence with no filler, so it is concise, but the brevity reflects under-specification rather than efficiency. The key scoping information is simply absent rather than front-loaded.

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 parameter documentation, the one-line description leaves too much unknown for a four-parameter authenticated tool. An agent would have to guess at credential requirements and what the returned inventory actually contains.

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% across four parameters. The description's mention of 'Shopify products' hints that product_id scopes the lookup, but it says nothing about shop_domain, api_key or access_token, which are the parameters an agent is most likely to misuse.

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 verb 'Get' and resource 'inventory for Shopify products' are present, but the description never specifies what inventory data means here (stock levels, per-location quantities, availability) or how it differs from the sibling shopify_products. An agent cannot tell the scope of the returned data from the text alone.

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 statement of when to use this tool, when not to, or which sibling (shopify_products, shopify_orders, shopify_collections) to prefer for a given question. Usage must be inferred entirely from the name.

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