zotero_delete_collection

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

With no annotations, the description carries the full disclosure burden. It explicitly reveals the key destructive nuance that collection deletion alone preserves items in the library and that the default behavior only removes folder membership. It does not describe reversibility or permission requirements, but the most decision-relevant behavior is transparent.

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 compact sentences with no filler. It front-loads the action, then gives the critical caveat about item preservation. Every word 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 low-complexity tool with only two params, a required collection key, and an output schema, the description is complete enough. It covers the action, the default behavior, and the escalation path for deleting items. Return values are already addressed by the output schema.

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%, so the schema already documents both parameters well. The description adds a little contextual meaning around delete_items ('by default they just lose this folder'), but does not introduce substantial new parameter semantics beyond what the input schema provides.

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 precise action and resource: 'Delete a collection.' It immediately clarifies scope by noting the collection's items are NOT deleted unless delete_items=true, distinguishing this from zotero_delete_items and from collection membership removal tools. The purpose is unambiguous and usefully scoped.

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 clear contextual guidance: by default, this tool only removes the folder, not the items, and setting delete_items=true escalates the operation. It stops short of explicitly naming alternatives like zotero_delete_items or zotero_remove_items_from_collection for when those should be used instead, so it is strong but not fully explicit.

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