Permanently delete Zotero items

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

Goes well beyond annotations (destructiveHint=true) by emphasizing permanence and irreversibility ('NOT the trash', 'purges'), disclosing auto-chunking to 50 keys, and noting the library version precondition. No contradictions with annotations.

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?

Exceptionally concise: two sentences pack critical warnings, alternative guidance, preconditions, and implementation details. Front-loaded with the most important warning about permanence.

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?

Fully covers the tool's complexity: purpose, irreversibility, alternative, server flag, confirm requirement, auto-chunking, and library version precondition. No output schema is needed as the action is self-explanatory.

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 50% (half of parameters have descriptions). The description adds minimal parameter context ('by key' for item_keys), but does not clarify library_id or library_type. Overall, no significant extra meaning beyond the schema for the unspecified parameters.

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's purpose: permanently and irreversibly delete Zotero items by key. It explicitly distinguishes this from the reversible trash operation, directly referencing the sibling tool zotero_trash_items.

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: 'Prefer zotero_trash_items, which is reversible.' Also details preconditions (server flag ZOTEUS_ALLOW_DELETE=true, confirm:true required), leaving no ambiguity about when and how to use this tool safely.

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