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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral detail beyond that: long text fields are truncated at 25,000 characters, an unknown id returns { error }, and the citation string is generated from the returned fields because items rarely carry their own citation.

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?

Front-loaded with purpose and efficient overall; the long but informative field enumeration and the two trailing sentences (citation generation, truncation/error) all carry useful content. Slightly dense as a single run-on field list but nothing is wasted.

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?

With no output schema, the description carries the full burden of describing returns, and it does so thoroughly: the metadata field list, the generated citation/bibtex/ris/csl-json outputs, the truncation limit, and the error shape. An agent has everything needed to call and interpret this 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 100%, so both parameters are already documented in the schema, including the id format and the citation_format enum mapping. The description restates that citation_format swaps BibTeX for RIS or CSL-JSON, adding framing but little beyond the schema, so the baseline 3 applies.

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?

States a specific verb (get) and resource (one research item) and then enumerates the exact payload an agent receives: dates, contributors, subjects, places, collections, citation fields, etc. This clearly distinguishes it from sibling list/search tools like search_research_items and get_collection_overview.

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?

Usage is implied by the name and the 'full metadata for one research item' framing plus the id-based signature, so an agent can infer this is the detail-fetch counterpart to search. However, there is no explicit guidance on when to prefer this over the sibling get_* tools or a signal to call search_research_items first to obtain an id.

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