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

Annotations already declare readOnly, idempotent and openWorld, so the description only needs to add context — which it does by disclosing the batch limit and, importantly, the partial-failure behavior ('Inputs it cannot match come back in unresolved with a reason'). It does not cover rate limits, auth requirements, or ordering of results.

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 identifier formats and returned fields are front-loaded in the first sentence, with scope exclusion and error behavior following. It is dense but every clause carries information; the field list is slightly long given an output schema exists.

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?

For a single-parameter batch lookup with full annotation coverage and an output schema, this leaves nothing an agent needs to call it correctly: accepted identifiers, batch cap, scope exclusion, and unresolved-input handling are all present.

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% and the single parameter already documents all four accepted identifier forms, so the baseline is 3. The description adds only the 'W…' OpenAlex prefix hint and the 1–100 cap, which largely restate the schema.

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 and resource ('Fetch OpenAlex records ... by DOI, OpenAlex ID (W…), PMID or PMCID') and enumerates the returned payload. The clause 'It does not use the citation graph' separates it from the graph-oriented siblings without naming one.

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 does not use the citation graph' implicitly routes citation-graph needs to query_citation_graph/explore_citation_network, and the batch cap of 100 gives a concrete usage boundary. No sibling is named explicitly and there is no explicit when-not guidance, so it stops short of 5.

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