ncbi_esummary

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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as read-only nature, authentication needs, rate limits, or side effects. For a fetch tool, mentioning it is read-only would improve transparency.

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?

The description is well-structured with Args and Returns sections, and the purpose is front-loaded. It is efficient with no wasted words, though it could be slightly shorter without losing clarity.

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 no output schema, the description mentions returning parsed JSON, which is adequate. However, it lacks information on error handling, required authentication, or any prerequisites. With zero annotations, more detail would be beneficial.

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 0%, so the description must compensate. It explains the `ids` parameter format (list or comma-separated) and notes `db` is an alias for `database`. However, the `database` parameter is only named without further explanation beyond 'NCBI database name.'

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 summary information for given IDs using esummary, and distinguishes it from sibling tools like ncbi_efetch (full records) and ncbi_esearch (search). The verb 'fetch' and resource 'summary information' are specific.

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?

The description explicitly says 'Useful for getting detailed info after esearch,' providing context for when to use this tool. It does not explicitly state when not to use it, but the sibling tools offer alternatives like ncbi_efetch for full records.

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