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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the danger profile is known. The description adds real value beyond that by flagging 'PERMANENT', the item-locking side effect, and the confirm_required response when confirm is missing. It says nothing about partial-failure behavior or whether locked items are recoverable via unlock_ad_items, which matters for a bulk destructive call.

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 short clauses, front-loaded with the destructive scope before the usage guidance and the confirm gate. Capitalization is used for emphasis rather than padding, and no sentence is wasted, though the all-caps style is slightly noisy.

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 tool with no output schema, the description covers scope, permanence, the locking side effect, and the confirmation flow — enough to call it safely. Remaining gaps are the meaning of project_id and what the caller gets back on success, both minor against the annotations that already carry the safety profile.

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 the schema already documents ad_id and confirm, including the confirm_required outcome; the description only restates the confirm gating. project_id has no description in either the schema or the description, so one of three parameters remains opaque.

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 with explicit scope: 'remove EVERY item from the LIVE ad channel and lock them'. The caps on EVERY and the 'LIVE' qualifier separate it from partial removal, and 'lock them' hints at the post-state. It never names the nearest sibling (remove_ad_items), so the contrast is implied rather than stated.

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?

'Use this when the user asks to take all listings down' gives a concrete triggering condition, and the confirm:true requirement adds a procedural gate the agent must satisfy. There is no explicit when-not clause or named alternative for the partial-removal case, so the agent must infer that remove_ad_items is the non-bulk counterpart.

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