zotero_item

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

With no annotations, the description carries the burden of explaining behavior. 'Show' implies a read-only lookup, and the description adds useful content expectations, but it does not explicitly say the operation is non-mutating or describe not-found/error behavior. The output schema covers return structure, so this is adequate but not rich.

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 short and front-loaded with the core idea: viewing a single item's full metadata. The bilingual repetition adds no new information, but it is compact enough that it does not become wasteful.

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 lookup tool with an output schema, the description covers the purpose and highlights key result contents. It does not explain how to obtain a valid item_key or what happens if the item is missing, but those gaps are minor given the tool's simplicity and available schema.

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 description coverage is 0%, so the description must compensate for the undocumented item_key parameter. The phrase 'one item' ties the key to the item whose metadata will be shown, but the description does not explain the key's format or how to obtain it. For a single required parameter, this is enough to call correctly, though minimally.

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 states a specific verb ('Show') and resource ('full metadata for one item'), and names distinguishing contents such as abstract and attachment list. This separates it clearly from sibling tools like zotero_search and zotero_collection_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?

The intended context is implied: use this when you have a single item key and need that item's full metadata. However, it does not explicitly say when to prefer this over zotero_search or zotero_recent, and it provides no exclusions or alternatives.

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