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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the destructive nature is covered by structured data. The description adds nothing beyond that – no mention that deletion is irreversible, that a confirmation token round-trip is required, or what happens to the SKU on error.

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?

Four words is not conciseness here but under-specification; the brevity comes at the cost of omitting required operational context for a destructive, two-phase operation. A front-loaded safety note would have earned its place with no real length cost.

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 with no output schema and a hidden confirmation-token workflow, the description leaves the agent unable to call it correctly on its own. The critical fact – that a bare call may only preview and requires resubmission with confirm_id – is only discoverable from a parameter description, not the tool description.

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 67%, below the 80% threshold, so the description is expected to compensate and does not. It says nothing about sku (undescribed in schema), account_id resolution, or the confirm_id preview/execute protocol that governs whether the call actually writes anything.

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 "Delete a listing" is a verbatim restatement of the tool name and title, giving no additional specificity about scope, target marketplace, or what a "listing" means here. It does not distinguish this tool from bulk_delete_listings, which is the obvious sibling an agent must choose between.

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 guidance on when to use this versus bulk_delete_listings or update_listing. Nothing tells the agent about the two-step preview/confirm flow implied by the confirm_id parameter, which is the single most important usage fact for this tool.

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