zotero_delete_collection

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

With no annotations at all, the description carries the full transparency burden. It explicitly discloses the most important non-obvious behavior: deleting a collection does not delete its items. It also discloses a guard condition ('Refuses if the collection has subcollections') and mandates user confirmation, giving the agent essential behavioral context.

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?

Three short sentences with no filler. The main action is front-loaded, and every subsequent clause adds meaningful information: non-destructive behavior, an edge-case guard, and a required confirmation step.

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?

The description covers the core semantics and critical failure condition, which is enough for an agent to invoke the tool correctly. It does not describe the success/failure response format, which would be useful since there is no output schema, but this is a minor gap for a delete 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific detail beyond the general notion of a 'collection'; the schema already explains library and collection formats thoroughly.

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 action ('Delete a collection') and the key semantic nuance: items in the collection are NOT deleted and remain in the library and other collections. This distinguishes it from item-removal or item-manipulation tools, even without naming siblings.

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 strong operational guidance: confirm with the user first and expect refusal when subcollections exist. However, it never explicitly identifies alternatives or says when NOT to use this tool versus related tools like zotero_remove_from_collection or zotero_update_collection, so routing guidance is mostly implied.

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