delete_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond the obvious by stating that items are NOT deleted and that UNSAFE_OPERATIONS must be set to 'all', which are critical side effects and prerequisites. It does not mention irreversibility or subcollection behavior, but the key behaviors are well covered.

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?

Two sentences, no fluff, front-loaded with the action, followed by the key caveat and a security requirement. Every sentence contributes meaningful information.

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 single-parameter delete operation with no output schema and no annotations, the description covers purpose, side effects, and a prerequisite. It does not describe the return value or success/failure behavior, but for a simple void-like operation this is acceptable, making it nearly 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?

Schema coverage is 100% and the schema itself explains that collection_key is the Zotero collection key and how to get it (from get_collections). The description adds no additional parameter-specific meaning, so the baseline score of 3 is appropriate.

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?

Clearly states 'Delete a collection (folder)' with a specific verb and resource, and adds the critical caveat that items inside are not deleted. This distinguishes it from sibling tools like delete_items and provides precise intent.

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?

Provides clear context for when to use the tool (deleting a collection) and the important consequence that items remain in the library. It does not explicitly name alternatives or when-not-to-use, but the caveat implicitly discourages use if item deletion is intended, which is sufficient for a 4.

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