Etsy MCP Server

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

No annotations are provided, so the description carries full burden. It states 'Update' implying a mutation, but doesn't disclose behavioral traits like required permissions, whether it overwrites or merges inventory, error handling, side effects (e.g., affecting listings), or response format. This is inadequate for a mutation tool with complex nested parameters.

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?

Single sentence, front-loaded with the core action. It's efficient with no wasted words, though slightly vague (e.g., 'update' could be clearer as 'modify' or 'set'). Structure is straightforward but lacks detail for a mutation tool.

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 complexity (mutation tool with nested objects, no annotations, no output schema), the description is incomplete. It doesn't cover behavioral aspects, error cases, or what success looks like. For a tool that modifies inventory with intricate parameters, more context is needed to guide safe and correct usage.

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 100%, so the schema documents parameters well. The description adds minimal value beyond the schema by mentioning 'products with offerings and prices', which loosely maps to the 'products' array and its nested 'offerings', but doesn't explain semantics like what 'property_values' represents or how updates are applied. Baseline 3 is appropriate given high schema coverage.

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 verb 'Update' and resource 'inventory for a listing', specifying it involves 'products with offerings and prices'. It distinguishes from siblings like 'get_listing_inventory' (read vs write) and 'update_listing' (general vs inventory-specific). However, it doesn't explicitly mention it's a mutation tool or contrast with all relevant siblings like 'create_draft_listing'.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a listing_id from get_listing), when not to use it (e.g., for initial creation vs updates), or direct alternatives like update_listing for non-inventory changes. The context is implied but not explicit.

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