delete_collection

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

The annotation already marks destructiveHint=true, so the agent knows the operation is destructive. The description adds 'Requires ADMIN,' which is an authorization context not covered by annotations. This adds meaningful behavioral information beyond what the structured data provides, though it does not detail other side effects like irreversibility or cascading behavior.

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 two short sentences totaling nine words, with the primary action front-loaded. There is no redundancy or unnecessary detail, making it highly concise and well-structured.

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, the description lacks critical context such as whether deletion is irreversible, what happens to items within the collection, or failure conditions (e.g., non-empty collections). While the output schema and destructiveHint annotation provide some context, the description alone is insufficient for an agent to fully understand the consequences of the operation.

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 a single required property, collection_id, with no schema-level description (0% coverage). The tool description does not mention the parameter or provide any additional guidance, leaving the agent to infer its meaning only from the parameter name. Since schema coverage is low, the description should compensate but does not.

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 begins with the specific action 'Delete a collection,' clearly stating the verb and resource. This distinguishes it from sibling collection tools like create_collection, update_collection, and list_collections, making the purpose unambiguous.

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 provides a clear usage prerequisite by stating 'Requires ADMIN,' which tells the agent when the tool can be invoked. It does not explicitly name alternatives or exclusions, but the resource scope is evident from the description. The context is clear enough for basic selection.

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