Delete Collection

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

Annotations already flag this as destructive; the description adds that deletion is 'permanently and irreversibly' done and 'subject to existing Container guards', providing valuable context beyond the annotations. It also notes that confirmation is required, which is not in the 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 a single sentence that starts with 'CONFIRMATION REQUIRED', immediately conveying a critical prerequisite. Every word contributes meaning; there is no redundancy or fluff.

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 one-parameter delete tool with no output schema, the description covers the essential behavioral aspects: permanence, irreversibility, container guards, and confirmation requirement. It doesn't detail side effects on associated data or error handling, but given the tool's simplicity, this is reasonably complete.

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?

The input schema has one parameter (collection_id) with no description coverage. The description only refers to 'this Collection' and doesn't explicitly explain that collection_id is the identifier of the collection to delete. However, the schema provides the uuid format, and the parameter is singular and self-evident for a delete operation, so the description adds minimal but acceptable meaning.

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 the tool deletes a Collection, using a specific verb and resource. It distinguishes itself from sibling delete tools by explicitly naming the target resource.

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 implies this tool is for deleting collections, but it does not explicitly compare against alternative delete tools or provide when-to-use vs when-not-to-use guidance. It mentions 'CONFIRMATION REQUIRED' and 'Container guards' as prerequisites/constraints, but these are not alternative-selection guidelines.

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