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

With no annotations, the description carries the burden, and 'Soft-delete' usefully signals a reversible/hidden deletion rather than a permanent one. It does not, however, describe what happens to the listing's visibility, whether it can be restored, or what response the caller should expect.

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 six-word sentence conveys the action, resource, and ownership restriction with no filler. It is front-loaded and easy to parse.

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 two-parameter tool the description is adequate for selecting and invoking the call, but without annotations or an output schema it leaves out soft-delete semantics (e.g., visibility/restoration) and any permission details beyond the api_key parameter. A short sentence on the effect would make it complete.

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%, so both id and api_key are already documented in the schema. The description adds no parameter-level meaning, which matches the baseline for fully covered parameters.

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 uses a specific verb ('Soft-delete'), names the resource ('a listing'), and adds the scoping condition 'you own.' This clearly distinguishes it from siblings such as update_app and publish_app.

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?

It provides clear context: the tool should be used to soft-delete listings that the caller owns. It does not explicitly name alternatives or say when not to use it, but the ownership qualifier offers practical selection guidance.

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