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

Without annotations, the description carries the burden of disclosure. It reveals the data source (OpenAlex), scope (240M+ works, arXiv/preprints/conference/journal), ranking logic (citations + recency + relevance), return content (titles, abstracts, citation counts, authors), and a fallback to Semantic Scholar. It also discloses pricing. It doesn't mention rate limits or error handling, but overall it is quite transparent.

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 description is front-loaded with purpose, uses three concise sentences plus a pricing note. Each sentence earns its place: purpose, use case, fallback, and cost. There is no fluff or redundancy.

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?

Given the tool's moderate complexity (5 params, no output schema), the description tells the agent what it returns (top N papers with abstracts, citations, authors), where data comes from, how results are ranked, and when to use it. This is sufficient for an agent to invoke the tool correctly without needing an output schema.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description adds minimal extra parameter context, only reinforcing that ranking uses citations/relevance/recency and that min_citations with 50+ surfaces well-known work. It doesn't provide syntax or formatting details beyond 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?

The description opens with 'Research intel — has someone solved X already?' which immediately conveys the tool's purpose: searching academic literature for prior art. It specifies the verb 'Queries' and the resource '240M+ academic works via OpenAlex,' and clearly distinguishes itself from the sibling tools (payments, attestations, registry, etc.).

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 description states it is 'Built for autonomous agents that need to check prior art before burning cycles re-deriving a known result,' providing a clear when-to-use scenario. It does not explicitly mention when not to use it, but the sibling tools are so distinct that no exclusions are necessary.

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