zotero_get_metadata

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the basic effect ('Get detailed metadata') and adds no details about what metadata is included, whether the item must exist, error behavior, or access requirements. The word 'Get' hints at a read-only operation, but little else is disclosed.

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 short sentence with no filler or redundancy. It is front-loaded with the action and object, making it easy to parse quickly. Given the tool's simplicity, this level of conciseness is appropriate.

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?

This is a simple one-parameter read tool, and the description names the core purpose. However, there is no output schema, so the description should clarify what 'detailed metadata' means or what fields the agent can expect, and it does not. The gaps are minor but present for a tool with no annotations or output 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?

The input schema fully documents the only parameter (item_key as 'Zotero item key'), so schema coverage is 100% and the baseline of 3 applies. The description adds no additional parameter meaning, but that is acceptable because the schema already provides sufficient semantic information.

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') and resource ('detailed metadata for a specific paper'), making the tool's function immediately clear. It also distinguishes it from sibling tools like zotero_search, zotero_get_fulltext, and zotero_list_collections by focusing on metadata retrieval for one known item.

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 explicit guidance is given about when to use this tool versus alternatives, nor are any exclusions or sibling comparisons mentioned. The phrasing 'for a specific paper' implies use when an item key is known, but an agent is not told when to prefer this over zotero_search or zotero_get_fulltext.

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