Delete a listing

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

Beyond the annotations (destructiveHint), the description adds critical behavioral context: the deletion is irreversible, and specifically the item, photos, and stats are permanently gone. It also discloses the confirmation requirement, enriching the annotation-provided safety signal.

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 compact and well-structured, leading with the primary action, then irreversible consequences, then usage constraint and alternative. Every sentence adds value with no redundancy or fluff.

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 destructive mutation tool with no output schema, the description provides sufficient context: it defines the action, irreversibility, what data is lost, and the mandatory confirmation guardrail, covering the essential aspects an agent needs to invoke it correctly.

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 schema already documents confirm and country, and the description adds no substantial new parameter semantics beyond restating the confirm requirement. The itemId parameter remains undocumented in the description, though schema coverage is moderate at 67%.

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 permanently deletes one of the user's Vinted listings, using a specific verb and resource. It also explicitly distinguishes this from deactivate_listing, making the purpose unambiguous.

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?

Provides explicit when-to-use guidance (after exact user confirmation) and when-not-to-use guidance, directing users to deactivate_listing for catalogue-only removal. It also specifies the prerequisite that confirm must be true only after explicit user consent.

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