Move Zotero item to trash

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

Annotations mark the tool as not read-only and not destructive; the description adds a useful qualifier that the item is never permanently deleted, reinforcing destructiveHint=false. However, it does not disclose other behavioral details such as idempotency, reversibility, or permission requirements.

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?

Two short sentences with the core action first and the safety qualifier second; every word earns its place. The description is appropriately sized for a single-parameter mutation.

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 simple one-parameter mutation, the core action and non-destructive nature are covered, and the annotations provide the read-only and destructive hints. However, with no output schema and no guidance on the key source or expected response, the description is only minimally complete.

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?

The only parameter is 'key', whose name suggests a Zotero item key, but with 0% schema description coverage the description provides no explanation of what the key represents, where to find it, or any format beyond minLength 1. The description adds no semantic value beyond the 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?

Description names a specific verb ('Move'), a distinct resource ('Zotero trash'), and the object ('an item'), clearly differentiating it from sibling tools like create_item, update_item, and search_items. It does not merely restate the title.

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?

No guidance is given about when to use this tool versus alternatives such as update_item or permanent deletion flows. Prerequisites like item existence, ownership, or how to obtain the key are also absent, leaving usage context to inference.

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