etsy_listing_offering_get

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

The description is consistent with the readOnlyHint annotation but adds no additional behavioral details. No mention of rate limits, required scopes, or side effects beyond what annotations already indicate.

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, front-loaded with the action, and uses minimal words. It is concise but slightly under-specifies for the tool's complexity.

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?

Given three required parameters, no output schema, and only a readOnly annotation, the description is insufficient. It does not explain how to get the IDs, the relationship to other tools (e.g., etsy_listing_product_get), or what the response 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?

The input schema has three parameters with no descriptions, and the tool description adds no explanation of what each parameter (listing_id, product_id, product_offering_id) represents or how to obtain them. The schema coverage is 0%, and the description fails to compensate.

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 it retrieves a specific offering (price/quantity for a variation) on a listing, using a specific verb and resource. It distinguishes from sibling tools that get listings, products, or inventory, as it targets a specific offering.

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?

No explicit guidance on when to use this tool versus alternatives like etsy_listing_inventory_get or etsy_listing_product_get. The description implies it's for a specific offering but does not provide context on prerequisites or when it's appropriate.

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