Zotero Delete Collection

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

With no annotations provided, the description carries full disclosure burden. It clearly states that items inside are NOT deleted, subcollections ARE deleted, and that the delete is hard and irreversible via the API. This is exemplary transparency for a mutation operation.

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 well-organized: purpose first, then side effects, irreversibility, and prerequisite. Each sentence earns its place. It's slightly long but not verbose; the example is helpful and adds clarity.

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 delete operation with a single parameter and no annotations, the description covers all necessary aspects: what it does, side effects, undoability, how to obtain the required key, and an example. Nothing essential is missing.

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 schema provides no description for collection_key (0% coverage), but the description compensates by specifying the key format ('8-character key') and giving a concrete example (KMMQDFQ4). This adds meaningful semantic value beyond the bare schema.

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 states a specific verb and resource ('Delete a collection (folder) from your Zotero library') and clarifies it operates on collections by key, distinguishing it from sibling deletion tools like zotero_delete_item and zotero_delete_annotation. The 8-character key detail adds precision.

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?

It explicitly instructs the agent to use zotero_search_collections to find the key first, which is a clear prerequisite and usage hint. It doesn't explicitly state when not to use this tool, but the resource type (collection vs item/annotation) implicitly differentiates it from other delete tools.

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