Delete Collection

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

The description adds valuable context beyond the destructiveHint annotation by explicitly stating the operation is permanent and that items remain in the library. This clarifies the scope of destruction, which is useful for an AI agent. However, it does not mention potential edge cases like subcollections, so it is not fully comprehensive.

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 no wasted words. It leads with the purpose, adds one crucial clarification, and lists the parameter cleanly. Every sentence earns its place.

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 simple one-parameter delete operation, the description covers the essential behavior and the most important caveat (items are not deleted). An output schema exists, so return values are not needed in the description. It lacks details on subcollection behavior and permissions, but these are not critical for basic usage.

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 0% schema description coverage, the description carries the full burden for parameters. It does provide minimal added meaning by calling collection_id 'the collection key', which gives some semantic context about the identifier. However, it does not explain the format or how to obtain the key, so it only partially compensates for the schema gap.

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 opens with a specific action and resource: 'Permanently delete a collection from your Zotero library.' It clearly distinguishes this from other delete tools (delete_note, delete_annotation, delete_item) by specifying 'collection' and immediately clarifying that items are not deleted, which is a key differentiator.

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 context is clear: this tool is for deleting collections, not the items within them. The note that 'Items in the collection are NOT deleted' implies that users wanting to delete items should use a different tool, but it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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