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

The description proactively reconciles the unusual annotation set: 'Reads or computes only; not marked read-only because each call is charged,' which directly explains why readOnlyHint is false for a non-mutating tool. It also discloses cost ($0.003/call via x402 USDC or card key), the free tier (first 25 free, failed calls free), result cap, and that results are open-world — behavior an agent cannot infer from the annotations alone.

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-loads purpose, then returned fields, filters, use cases, an example, and pricing. Every sentence carries information relevant to calling the tool correctly, though the pricing/auth sentence is dense enough that the definition runs long for a 3-parameter tool.

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?

No output schema exists, so the description correctly documents the return fields, scope, and result cap itself, and it covers the two things an agent would otherwise be blind to: cost/auth requirements and the read-only-vs-charged tension. Nothing needed to invoke this tool is missing.

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%, so baseline is 3; the description exceeds it by stating the 20-result ceiling and supplying a worked example (query=CRISPR off-target effects, limit=5, fromYear=2020) that shows how the three parameters combine. It does not, however, add semantics beyond the schema for query string length or fromYear boundary behavior.

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 — 'Search scholarly literature across journals, conferences, preprints and books' — and enumerates the returned fields (title, authors, year, venue, citation count, DOI link, abstract). This clearly separates it from siblings like wikipedia, dictionary, feed and pdf_text, which handle encyclopedic, lexical, or document-level content rather than literature 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?

Gives concrete scenarios: research agents, literature reviews, fact-checking a claim against published work, finding a DOI. That is strong positive guidance. It stops short of naming an alternative for cases where a general encyclopedia (wikipedia) or a specific document (pdf_text) is the better fit, so no explicit exclusions are stated.

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