Restore Item

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which tells the agent this is a write operation with no destructive effect. The description adds the scope 'from Zotero's trash' but does not disclose additional behavioral traits such as permissions required, whether attachments are restored, or behavior for invalid item keys. With annotations available, the description provides marginal added context.

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 a single, front-loaded sentence that directly states the action and object. It contains no filler or redundant information, making it highly concise and well-structured.

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 tool with one parameter, annotations, and an output schema, the description is minimally viable but has gaps. It does not explain what happens if the item is not in trash, whether restoration is to original collections, or any error conditions. These missing details prevent full contextual completeness even though the core purpose is clear.

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 input schema has one parameter (item_key) with no description, and schema description coverage is 0%. The description does not mention the parameter at all, leaving the agent to rely solely on the parameter name 'item_key' for meaning. It fails to compensate for the lack of schema documentation, so it adds no 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?

The description 'Restore an item from Zotero's trash' clearly states a specific verb (restore), the resource (item), and the location (trash). It distinguishes itself from siblings such as trash_item and delete_item by clarifying the action is the inverse of trashing.

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 implies usage context (items in trash) but does not explicitly state when to use this tool versus alternatives (e.g., re-creating an item) or when not to use it. No exclusions or alternative tool references are provided, so the guidance remains implicit.

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