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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered; the description then adds genuinely new behavioral facts an agent needs: server-wide 3 req/s NCBI throttle, an extra NCBI call when abstracts=true, publisher-copyright caveat on abstracts, and a $0.01 USDC per-successful-call x402 payment requirement. Cost and rate-limit disclosure on a paid, throttled tool is exactly the kind of context annotations cannot convey.

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?

Purpose is front-loaded in the first clause, with return fields, query semantics, throttling, and payment following in a logical order. The single dense paragraph carries a lot, and the trailing HTTPS/x402 endpoint note is slightly bulky, but every sentence conveys operational information rather than filler.

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 takes on the burden of describing returns and does so field-by-field (PMID, title, authors, journal, dates, volume/issue/pages, DOI, PMCID, publication types, optional structured abstracts). Combined with throttle, pricing, defaults, and query syntax, an agent has everything needed to call this correctly without trial and error.

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 the baseline is 3, but the description adds real semantics: it clarifies that abstracts default to false and why (copyright, extra call), that the 'date' sort means newest-first, and that the date range is a publication-date filter. It does not document the `q` alias or the 1-50 limit bounds beyond what the schema already says, so it is an increment rather than a full substitute.

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 (Search) and resource (PubMed biomedical literature) plus the underlying API path (esearch + esummary + efetch) and enumerates exactly what is returned (PMID, title, authors, journal, DOI, PMCID, publication types). An agent can distinguish this from arxiv_search or openalex_search purely on the biomedical/PubMed scope without opening the schema.

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 usage conditions: full PubMed query syntax with [MeSH]/[Author] tags, relevance vs newest-first ordering, publication-date range, and that abstracts are off by default and should be requested only when needed. It stops short of naming alternatives (arxiv_search, openalex_search, clinical_trials) or stating when not to use it, so it does not reach a 5.

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