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

Annotations already declare destructiveHint, non-idempotent and open-world, so the safety profile is partly covered. The description still adds real value beyond that: it discloses that items are 'locked', that the effect is 'PERMANENT', and that the operation is marketplace-wide rather than scoped — details an agent cannot infer from the hints alone.

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?

Three tight clauses, each front-loaded with the highest-risk fact first (scope, permanence, confirmation). No filler and nothing buried mid-sentence.

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 bulk operation with no output schema, the definition covers scope, irreversibility, locking side effect, and the confirmation gate — enough for correct invocation. It does not explain what project_id narrows or what happens to items that are already locked, leaving a small gap.

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% and both marketplace_id and confirm are already documented in the schema, including the confirm_required failure mode. The description reinforces the confirm gating but adds no syntax or scope meaning for project_id, which is the one undocumented parameter. Baseline 3 is appropriate.

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?

States a specific verb and resource plus its scope in the very first clause: 'MARKETPLACE-wide remove all — remove EVERY item from the LIVE marketplace'. Capitalized emphasis on 'EVERY' and 'LIVE' separates it from the partial remove_marketplace_items and from ad-side remove_all_ad_items.

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?

Gives an explicit trigger ('Use this when the user asks to take all listings down') and a prerequisite workflow (confirm:true only after the user agrees), which the sibling partial-removal tool does not require. It stops short of naming remove_marketplace_items as the alternative for selective takedowns, so the boundary is implied rather than spelled out.

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