zotero_delete_items

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly explains that the tool does not perform a true DELETE but marks items as deleted, that the operation is recoverable, and that permanent purge requires a separate workflow. This is transparent and contradicts nothing.

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 three dense, useful sentences: the main action, the API caveat, and the usage/confirmation requirement. It is front-loaded and contains no filler or repetition of the tool name.

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?

Given the output schema and fully documented parameters, the description covers selection, safety semantics, recoverability, the confirmation guard, and the permanent-purge alternative while naming relevant sibling tools. Nothing critical is missing for correct invocation.

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%, with both item_keys and confirm already documented. The description reinforces that confirm must be true but adds little semantic detail beyond the schema, 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?

The opening phrase 'Move items to Zotero's trash' states a clear verb, resource, and target state. It also immediately distinguishes this tool from permanent deletion by naming zotero_restore_items as the recovery path, so an agent can tell it apart from zotero_empty_trash and zotero_delete_collection.

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 explicitly says 'Use for duplicates' and gives a concrete alternative for permanent removal: 'list the trash and empty it with zotero_empty_trash.' It also flags the invocation requirement confirm=true, leaving little ambiguity about when or how to call this tool.

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