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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description still adds meaningful behavior: a Crossref fallback when OpenAlex is unavailable, per-call pricing ($0.01 USDC via x402 on Solana), and an equivalent HTTPS endpoint. It does not cover rate limiting or failure semantics beyond the fallback, but the payment and degradation behavior are genuinely useful disclosures.

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 the core capability and entity types, then layers on filters, fallback, price and endpoint in sequence. It is dense but every clause carries information; only the repeated field enumeration is slightly verbose relative to the schema.

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 compensates by enumerating return fields for all three entity types (title, authors + ORCID + institutions, DOI, citation count, OA URL, abstract; h-index and topics for authors; ROR and country for institutions). Combined with the fallback and payment details, an agent has everything needed to call it correctly and interpret results.

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 every parameter (q, oa, from/to, page, sort, type, limit, abstracts) is already documented, establishing the baseline of 3. The description's recap of 'Year range, open-access filter, sort by relevance/citations/date' mostly restates the schema and adds no syntax or format detail beyond it.

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 — 'Scholarly search over OpenAlex (250M+ works)' — and enumerates the three entity types it handles (works, authors, institutions) along with the fields returned for each. It is clearly distinguishable from sibling search tools by naming the OpenAlex data source, though it does not explicitly contrast itself with arxiv_search or pubmed_search.

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 through the type enumeration ('works ... or authors ... or institutions') and the mention of year range, OA filter and sort, but there is no explicit statement of when to pick this over the other scholarly-search siblings or when-not to use it. The agent must infer selection from the provider name alone.

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