etsy_listing_inventory_get

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that it returns variations, prices, quantities, and SKUs, which is useful context. However, it does not describe pagination, response structure, or the effect of shows_scaling parameter, which are behavioral gaps beyond the annotations.

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 sentence that concisely states the tool's purpose and key return data. It is efficient and front-loaded, but could be slightly improved by structuring into a brief summary and usage note.

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 output schema, the description partially fills the gap by listing return fields (variations, prices, quantities, SKUs). However, it does not address pagination, limits, or the role of shows_scaling, leaving the tool somewhat incomplete for an agent to use confidently without further inference.

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 carries full burden for parameter explanation. It only mentions listing_id implicitly through the purpose, but does not explain shows_scaling at all. The meaning of this boolean parameter remains unclear, reducing the description's value for parameter semantics.

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 retrieves inventory/products for a listing, specifying key fields (variations, prices, quantities, SKUs). It distinguishes itself from sibling tools like etsy_listing_inventory_update or etsy_listing_get by focusing specifically on inventory 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?

The description implies usage for reading inventory via the verb 'Get', but does not explicitly state when to use this tool versus alternatives like etsy_listing_get or etsy_listing_inventory_update. No exclusions or context are provided, leaving room for ambiguity.

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