Get one Zotero item

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds behavioral detail about the return format (Markdown metadata plus APA citation) and the include_abstract option, which is beyond annotations. It doesn't contradict annotations and provides useful context.

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 compact, well-structured with clear 'Args' and 'Returns' sections, and front-loaded with the purpose. No redundant sentences or filler. Every line earns its place.

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?

The tool is simple (fetch one item), and the description covers the key, the abstract flag, and the return format. An output schema exists, so detailed return structure is not needed. Nothing an agent needs to call it correctly 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?

Schema coverage is 0%, so the description carries the full burden. It explains item_key as an eight-character key returned by search tools, and include_abstract as controlling abstract inclusion. Both parameters are meaningfully described, exceeding the schema's minimal definitions.

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 clear verb ('Fetch') and resource ('full metadata of a single item by its Zotero key'), distinguishing it from sibling tools like search, get_children, and get_fulltext. The title is consistent, and there is no ambiguity about what the tool does.

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 description implies usage context: you need an item key from search tools, and it fetches full metadata. It doesn't explicitly mention alternatives or exclusions, but the context is clear enough for an agent to know when to select this tool. It falls short of a 5 because it doesn't contrast with zotero_get_children or zotero_get_collection_items.

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