zotero_delete_item

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

Discloses that trashed items are recoverable and that empty trash is needed for permanent deletion. Though no annotations are provided, the description covers the non-destructive nature (recoverable) and the default refusal for notes. Could mention permissions but overall sufficient.

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?

Concise with 4 sentences that front-load the purpose and scope. Minor redundancy ('Works for any item type') but overall efficient.

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 output schema exists (mentioned in context), the description covers key aspects: what it does, scope, sibling alternative, and recovery. Lacks mention of library/collection scope, but adequate for a simple delete tool.

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 has 100% coverage, so baseline 3. The description adds meaning by explaining the allow_note parameter's purpose and default behavior, and implies that item_key is the identifier. Adds value beyond 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 clearly states the tool moves a Zotero item to the Trash, works for any item type, and explicitly distinguishes from the sibling zotero_delete_note tool. The verb 'Move' and resource 'Zotero item' are specific.

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 explicit guidance: use this tool for any item type, for notes use zotero_delete_note, and allows overriding the note restriction via allow_note parameter. Also explains the recovery mechanism.

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