Get Zotero Item

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds value by disclosing error behavior ('Returns "Error: Not found (404)"') and describing the contents of the returned data ('type, creators, title, date, DOI/URL, abstract, tags, collections, notes count'), which is not covered by annotations.

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 well-structured with clear sections (Args, Returns, Examples, Error Handling) and is front-loaded with the core purpose. Every sentence earns its place, and examples are compact and illustrative without being verbose.

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?

Despite having no output schema, the description explicitly lists the fields returned and the optional bibliography behavior. It also covers error cases and points to the correct alternative tool. This makes it fully self-contained for an agent to decide when and how to call the 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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by providing usage examples that tie parameters to intents (e.g., 'give me an APA citation' -> include_bibliography=true, citation_style='apa') and clarifying the effect of response_format. This adds meaningful context.

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 ('Retrieve full metadata') and clearly identifies the resource ('a single item by its key'). It explicitly differentiates itself from sibling tools by stating 'Don't use when: searching by title/author (use zotero_search_items instead)'.

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?

Provides explicit when-to-use examples ('get the full record for item X42A7DEE', 'give me an APA citation') and an explicit exclusion with an alternative tool ('Don't use when: searching by title/author (use zotero_search_items instead)'). This is textbook usage guidance.

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