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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description does add real value beyond the annotations by disclosing the cascade scope ('all its rows') and irreversibility ('No undo'), but says nothing about permissions or what the response reports.

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 brief sentences, with the destructive scope front-loaded ahead of the irreversibility warning. Nothing is wasted.

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?

There is no output schema, but for a destructive delete the essential facts – cascade scope and no-undo – are present. Missing detail on permissions and result reporting is minor.

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 100%: both 'id' and 'slug' are documented in the schema. The description mentions the collection but adds no format, scoping, or precedence guidance (e.g., whether slug or id wins), so the 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 (delete) and resource (collection), and the phrase 'and all its rows' pins down the cascade scope that separates it from delete_collection_row. It stops short of naming that sibling, so an agent must infer the contrast.

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?

The description warns 'No undo' but never says when to use this versus delete_collection_row, update_collection_schema, or other collection tools. There is no explicit alternative routing or prerequisite (e.g., permission or site-scoping) guidance.

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