ncbi_efetch

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

The description discloses that it returns actual data in requested format, but with no annotations provided, more detail is needed. It omits behavioral traits like rate limits, authentication needs, or error handling for invalid IDs. Adequate but not thorough.

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?

Structured with Args and Returns sections, front-loaded with core purpose. Clear and efficient, though there is minor redundancy with db alias. Overall well-organized and concise.

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 5 optional parameters and no output schema, the description covers main purpose, parameters, and return format. However, it lacks error cases, prerequisites, or limitations. Adequate for a straightforward tool but not fully complete.

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?

With 0% schema description coverage, the description compensates well by explaining each parameter: database, ids (with format examples), rettype, retmode, and the db alias. Adds meaning beyond schema definitions, though could list more specific values.

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 clearly states the tool fetches full records using efetch, with a specific verb and resource. It distinguishes well from sibling tools like ncbi_esearch (search) and ncbi_esummary (summary), making purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that ncbi_esearch should be used first to find IDs, nor does it state when not to use efetch. The description lacks explicit context for selection among siblings.

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