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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description earns credit by adding "permanently" (irreversibility) and the explicit-user-request requirement, but says nothing about what happens to lists still attached to live campaigns or partial-failure behavior across multiple IDs.

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?

One sentence, front-loaded with the verb and the destructive qualifier, with the invocation constraint attached. Nothing extraneous and nothing buried.

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, fully-annotated, fully-documented two-parameter tool, the description covers what it deletes and when it may be called. The gap is outcome behavior on multi-ID or in-use lists, which is not addressed anywhere in the definition.

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%; listIds already names its source tool and channel documents the per-channel scoping rule in depth. The description adds no parameter-level meaning beyond the schema, so 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?

States a specific verb (permanently delete) and a precise resource scope (one or more *entire* negative keyword lists), which implicitly separates it from keyword-level siblings like remove_keywords_from_negative_list. No sibling is named explicitly, so it stops short of the top band.

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?

"Only when the user has explicitly asked" gives a concrete gating condition for invocation, which is meaningful for a destructive tool. It does not, however, point to alternative operations (e.g. deleting individual keywords, or deleting vs. archiving a list) if the intent is narrower.

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