etsy_listing_product_get

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

Annotations already provide readOnlyHint: true, and the description aligns by stating 'Get'. No additional behavioral traits (e.g., return format, pagination, authorization) are disclosed. The description does not contradict annotations, so a baseline of 3 is appropriate.

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 9-word sentence that efficiently communicates the tool's core function. No redundancy or unnecessary words.

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 read-only tool with two integer parameters and no output schema, the description covers the basic purpose. However, it lacks details about what a 'product variant' is or what the returned data contains, which could be important for an agent to use it correctly without fallback.

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 coverage is 0%, and the description provides no additional meaning for the two parameters (listing_id, product_id) beyond their names. The description does not explain their purpose or constraints, leaving the agent to infer from naming alone.

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 specifies the action ('Get') and the resource ('specific product variant for a listing'). Among many listing-related siblings, this uniquely identifies a getter for a product variant, distinguishing it from similar tools like etsy_listing_get or etsy_listing_inventory_get.

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 guidance is provided on when to use this tool versus alternatives. The description fails to mention prerequisites, context for use, or distinguish between different variant retrieval tools (e.g., etsy_listing_offering_get).

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