get_item_metadata

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

No annotations provided, so description bears full burden. It discloses that the tool accepts item ID, PDF attachment ID, or file path (auto-lookup parent), and lists returned fields. However, it omits error handling or limitations.

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?

Description is short and front-loaded with purpose, followed by parameter details. However, it is bilingual (Chinese and English) which may slightly reduce conciseness.

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?

Given one parameter and an output schema (though not shown), the description explains return values adequately. The parameter is fully documented, and the tool's behavior is clear for its simple purpose.

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 single parameter 'item_id' is described beyond the schema: it accepts numeric item ID, PDF attachment ID, or file path. This adds significant meaning, especially since schema coverage is 0%.

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 clearly states it retrieves complete metadata for Zotero items, listing specific fields (title, authors, year, journal, DOI). It distinguishes from sibling tools like list_zotero_items and search_zotero_items by focusing on single-item retrieval with full details.

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?

Description implies usage when full metadata for a specific item is needed, but does not explicitly state when to use versus alternatives or provide exclusions. No direct mention of alternative tools.

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