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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower; the description adds genuinely new operational context (keyless access, NCBI/NLM autocomplete index provenance, and the normalization authorities: NCBI Gene, MeSH, LitVar/dbSNP, NCBI Taxonomy). It omits rate-limit and result-shape details, but the added provenance is substantive.

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 the core purpose with inline mapping examples, then routes to dependent tools, then gives provenance, ending with a one-word performance note ("Keyless."). No sentence is redundant and all three sentences carry distinct information.

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 3-parameter, fully documented lookup with no output schema, the description covers purpose, output id format, downstream use, and source. It could say more about what a multi-match response looks like (and that limit controls that), but it is sufficient for correct invocation.

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, but the description adds meaning by showing what the query parameter actually produces (name -> normalized id plus source vocabulary and numeric id) and by enumerating the entity types the concept filter resolves against. This goes beyond the schema's field-level descriptions.

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 precise verb (resolve) and resource (gene/disease/chemical/variant/species/cell-line names) and names the exact output artifact (@GENE_BRCA1, MeSH D001943) with worked examples. It explicitly distinguishes itself from siblings pubtator_search and pubtator_relations by positioning itself as the id-producing step.

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?

"Use the id with pubtator_search and pubtator_relations" clearly states the downstream context and the reason to call this tool first. However, it does not state when-not to use it or how it differs from the sibling resolve_entity, leaving a small routing gap.

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