Delete listing

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

The description adds context beyond annotations: defaults to reversible unlisting, requires confirmation, and is [SENSITIVE]. However, annotations mark destructiveHint=false despite the tool's ability to permanently delete, which is a slight inconsistency.

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?

Two concise sentences: first states purpose and default, second adds sensitivity and confirmation requirement. No wasted words, 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?

Covers key behavioral aspects (default mode, confirmation) for a mutation tool with no output schema. Could mention error scenarios or post-unlist/delete state, but sufficient for basic 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 coverage is 50% (platform and confirmation_token described). The description adds meaning only for the mode parameter by explaining the unlist vs delete choice. Product_id and confirmation_token are not explained in the description.

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 'Remove' and the resource 'product', specifying the default mode (unlisting vs deletion). This distinguishes it from siblings like update_listing or create_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?

The description explains the default mode (unlist) and mentions that permanent deletion is an option, providing guidance on when to use each. However, it does not explicitly contrast with other tools like update_listing.

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