ncbi_efetch

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds that it returns actual data (sequences, records), which is useful but vague. It does not disclose pagination, rate limits, or format specifics, which are partially covered by schema parameters. No contradiction with annotations.

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?

Two short, front-loaded sentences: 'Fetch full records using efetch. Returns actual data (sequences, records, etc.)'. Every word earns its place, and the description is concise without unnecessary detail.

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?

The tool is relatively simple with full schema coverage and read-only annotations, but there is no output schema, so the description bears some burden to explain return values. It only vaguely says 'actual data (sequences, records, etc.)' and doesn't address retmode/rettype interplay or how IDs are accepted (though schema covers this). It is adequate but not rich.

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 parameters are already documented (db/database, ids, retmode, rettype). The description adds no additional parameter-level meaning, which aligns with the baseline of 3 when the schema covers all parameters.

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 states 'Fetch full records using efetch' with a specific verb and resource, and clarifies 'Returns actual data (sequences, records, etc.)'. It distinguishes from sibling tools like ncbi_esearch (search) and ncbi_esummary (summary) by emphasizing full record retrieval, though it could be more specific about which databases are supported.

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: the description suggests this tool is for fetching full records when actual data is needed, as opposed to summaries or search. However, it does not explicitly state when to use it over alternatives like ncbi_esummary or provide exclusion criteria, leaving the agent to infer from the name and sibling tools.

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