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

Annotations already flag destructiveHint=true and idempotentHint=true, so the bar is lower, but the description still adds real value: it names what gets destroyed (the stored links), the user-visible consequence (the section renders empty), and the recovery route (version history / restore_version). It omits whether the removed items themselves are recoverable and whether any confirmation or permission 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?

Two compact clauses with a semicolon split: destruction and consequence first, reversibility second. No filler, and the most decision-relevant fact (the section goes blank) is front-loaded.

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 covers blast radius and recovery, and the schema covers all inputs. It stops short of clarifying how this differs from delete_collection or whether dependent collection items are also removed, which is the remaining ambiguity an agent would hit before calling.

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?

All three parameters are fully documented in the schema, including provenance hints pointing at list_sites and list_dynamic_collections, so the baseline of 3 applies. The description contributes nothing parameter-specific beyond that.

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 ("Delete a collection and the links it stored") and describes the downstream effect on the site section. However, it never distinguishes itself from the sibling delete_collection, and the tool's 'dynamic' scope is only implied by the title, so an agent could pick the wrong delete variant.

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?

Usage is implied rather than stated: deleting removes the rendered section, and restore_version is named as the recovery path. There is no explicit 'when to use this vs delete_collection/delete_collection_item' or any precondition (e.g. confirm with the user first), which matters for a destructive tool in a crowded namespace.

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