zotero_get_item_metadata

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

No annotations are provided, so the description carries full burden. It describes the output (metadata fields) but does not mention any side effects, permissions, or error conditions. However, for a read-only metadata retrieval tool, this is largely sufficient and adds context beyond the bare schema.

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 compact sentences plus a tip, front-loaded with purpose and output details. No redundant words; every sentence adds value.

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?

An output schema exists (unseen) but the description lists key return fields. It lacks details about required input validation or error conditions, but the presence of sibling tools and the specific purpose make it adequately complete for a metadata retrieval tool.

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%, requiring the description to explain parameters. The description does not mention `item_key` (what it identifies) or `include_bibtex` (what it does). It only describes the return values, leaving parameter meaning entirely to the schema names.

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?

Clearly states the tool retrieves complete bibliographic metadata for academic citation and analysis. Lists specific fields returned (title, authors, abstract, journal/venue, DOI, date, tags). Differentiates from sibling tools by explicitly mentioning alternatives for annotations (get_item_children) and full text (get_item_fulltext).

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?

Explicitly tells when to use alternative tools: 'For reading annotations...use get_item_children; for full text use get_item_fulltext.' Also advises using a dedicated prompt for literature reviews instead of ad-hoc analysis, providing clear usage boundaries.

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