Trash or restore Zotero items

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

Description discloses that the operation sets a 'deleted' flag, is reversible, and goes to the cloud API. Annotations already indicate non-destructive (destructiveHint=false) and non-read-only (readOnlyHint=false), so description adds context about the flag and reversibility without contradiction.

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 sentences with no filler. The main action is stated first, followed by clarification, usage guidance, and parameter hints. Every sentence adds value.

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 tool with 4 parameters, no output schema, and moderate complexity, the description covers core behavior, distinguishes from siblings, and explains the flag mechanism. It lacks explanation of return values or side effects beyond 'writes go to the cloud Web API', but given the presence of sibling tools and annotations, this is a minor gap.

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% (item_keys and action have descriptions). Description mentions item_keys and optional action with default, but does not cover library_id or library_type. It adds some meaning beyond the schema but insufficiently compensates for the undocumented 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 specifies the action: 'Move items to the trash (the safe, REVERSIBLE default) or restore them.' It distinguishes from the irreversible sibling 'zotero_delete_items', making the verb-resource relationship and scope explicit.

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?

Explicitly advises when to use this tool: 'Use this instead of zotero_delete_items unless you truly need irreversible removal.' Also states default action and that writes go to the cloud Web API.

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