zotero_item_metadata

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

No annotations are provided, so the description must carry the behavioral transparency burden. The operation is clearly a read-only fetch ('Get'), and the description adds what the result contains. It does not address edge-case behavior such as invalid item keys, authentication requirements, or whether the metadata reflects live library state, which would strengthen transparency.

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 focused sentences: the first states the action and target, the second lists the included fields. There is no filler, no repetition of the tool name, and the core verb and object are front-loaded.

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 read operation with an output schema, the description is mostly complete. It states the input (item key), the purpose (complete metadata), and highlights several return categories. It could add a hint about key format or mention that searching is the way to find a key, but no critical call-blocking detail is missing.

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 schema provides only the property name 'Item Key' with no description (coverage 0%). The description says 'given the item key', which connects the single parameter to the purpose but still does not explain what an item key looks like or how to obtain it. For a one-parameter tool this is adequate, but it adds only minimal 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?

The description uses a specific verb ('Get'), names the resource ('complete metadata for a specific Zotero item'), and clarifies the scope by requiring an item key. It also lists included content ('citation key, publication details, identifiers, and timestamps'), which distinguishes it clearly from siblings like zotero_item_fulltext or zotero_search_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 phrase 'given the item key' implies the intended usage: the caller should already have a key and wants full metadata for that item. However, there is no explicit guidance about when to choose this over related tools like zotero_search_items or zotero_item_fulltext, and no exclusions are stated.

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