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

Annotations already set destructiveHint: true and idempotentHint: true. The description adds key behavioral details beyond annotations: it specifies that the action is irreversible ('cannot be undone'), clarifies that posts are preserved ('only the list and its ordering go'), and implies a confirmation step by emphasizing permanence. No contradiction with annotations.

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?

The description is extremely concise with four terse sentences, no filler, and front-loads the key action ('Delete one of your collections'). Every sentence is necessary: the first states the purpose, the second clarifies the non-destructive effect on posts, and the third warns of irreversibility.

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?

Given the simple input schema (single required parameter with good description), annotations covering destructiveness and idempotence, and an output schema present for return values, the description is complete. It provides all necessary context for safe usage of this deletion tool.

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?

With 100% schema coverage and only one parameter (collection_id) which already has a description ('The collection's UUID. Must be yours'), the description adds minimal parameter-specific value. It implicitly confirms the collection belongs to the user but the schema's description already covers ownership. The description's value lies more in the overall tool behavior than in parameter details.

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?

The description clearly states it deletes a collection and explains what happens to the posts within it, distinguishing it from deletion of individual posts. This differentiates it from sibling tools like colony_delete_post.

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 explicitly states usage context: it only removes the list and ordering, leaving posts untouched, and warns that it cannot be undone. This provides clear guidance on when to use this tool versus alternative tools for post deletion.

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