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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond repeating 'Delete' — critically, it never mentions the two-phase preview/confirm flow implied by the 'confirm_id' parameter, which is the most important operational behavior of this tool.

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?

At three words it is undeniably front-loaded and wastes nothing, but this is under-specification rather than conciseness — a destructive tool merits more than a bare verb phrase.

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 an irreversible, open-world destructive operation with no output schema and no annotations covering the confirmation mechanics, the description leaves the agent without the confirm_id workflow, permission requirements, or any indication of what is returned or whether deletion is recoverable.

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 only 67%, and the required 'sku' parameter carries no description in the schema or the tool description. The description gives no parameter information at all, so it fails to compensate for the gap on the one field the agent is required to supply.

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 states a specific verb ('Delete') and resource ('a listing'), so the core action is unambiguous. However, it does nothing to distinguish this from the very similarly named sibling 'bulk_delete_listings', and it omits scope (single SKU/seller listing) that would separate the two.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative (bulk_delete_listings) for multi-listing deletion. The agent must infer from the sibling list which tool applies.

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