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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description adds real value by warning that abstracts are present in only ~51% of records — a caveat that affects downstream planning. It also previews record shape (host-work details), but says nothing about behavior for a missing/invalid id.

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?

One dense sentence that front-loads the purpose and uses the parenthetical detail to scope the payload. No wasted framing; the parenthetical field list is slightly list-heavy but each element 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?

With no output schema, the description does the work of describing return contents and flags the incomplete-abstract caveat. Only gaps are not-found/error behavior, which is minor for a simple id lookup.

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 schema alone documents only that reference_id is a required integer. The description clarifies it is a single-reference id lookup, which is marginally useful, but does not say where ids come from (search_references results) or that the identifier is numeric.

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+resource: returns the full bibliographic record for one academic reference by id, and enumerates the returned fields (abstract, subjects, DOI/URL, host-work). An agent can tell this is a single-item detail lookup rather than a search, though it never names the sibling search_references it complements.

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 'by id' framing implies this is the follow-up call once an id is known, and the 51% abstract note signals it is not the tool for abstract-based discovery. However, no explicit when-to-use/when-not statement or named alternative (e.g., search_references) is given.

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