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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new context beyond that: abstracts are returned only 'when available', identifier aliases are 'verified', and Europe PMC coverage is biased toward biomedical/life-sciences publications — a real coverage limitation the agent needs.

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 sentences, no padding, and the most important information (what is returned) is front-loaded ahead of the identifier guidance. The second sentence is dense with two separate ideas but still earns its space.

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 an output schema present, the description need not detail return values, though it partially does anyway. It covers input contract and coverage scope; the only real hole is sibling disambiguation against read_paper/search_papers.

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 paper_id is fully documented in the schema, and the description largely restates the same identifier list. It adds no format hints or precedence rules for ambiguous IDs, so the baseline 3 for high-coverage schemas 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?

The description states a specific verb (return/inspect) and resource (normalized paper records) and enumerates the returned fields, so the agent knows exactly what it gets back. It does not, however, distinguish itself from the close sibling research_read_paper or research_search_papers, leaving the agent to guess which one to call.

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?

It specifies the accepted identifier types (arXiv, PMID, PMCID, DOI, canonical ID), which is actionable usage context. But it never says when to reach for this tool versus read_paper, search_papers or related_papers, nor any when-not condition, so routing remains implied rather than explicit.

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