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

Annotations already declare destructiveHint=true, so the safety profile is covered. The word 'permanently' usefully reinforces irreversibility, but the description says nothing about downstream effects (orders, purchases, sales history), authorization scope, or whether confirmation is required.

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?

A single front-loaded sentence with zero filler. It is efficient, though its terseness is arguably the source of the missing behavioral detail rather than a virtue in itself.

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, the description plus destructiveHint cover the basic shape. It falls short on consequences of deletion and failure modes, which an agent about to destroy data would want to know.

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%, including the api_key fallback explanation, so the schema carries parameter meaning. The description adds nothing about the id format or whether a non-existent id errors out; baseline 3 applies.

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?

A specific verb (delete) plus resource (listing) and a scope qualifier ('one of your listings', 'permanently') that separates it from get_listing and update_listing. It is clear what the tool does, though it relies on the sibling names rather than naming an alternative explicitly.

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 explicit guidance on when to delete versus deactivate/update, no prerequisite (ownership, active orders), and no stated conditions under which the call would fail. 'Permanently' hints at caution but the agent is left to infer the decision rule.

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