get_summaries

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

With no annotations provided, the description carries the full burden. It correctly conveys that the tool is a read operation (fetching summaries), but it does not disclose potential limitations, error behaviors, or required authentication. The description is adequate but lacks explicit safety or side-effect statements.

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 concise and front-loaded with the purpose. It consists of two brief paragraphs: the first explains the function and parameters, the second provides examples. Every sentence adds value without redundancy.

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 the tool has an output schema (not shown), the description need not detail return values. It adequately covers purpose, parameters, and provides examples. However, it lacks information on prerequisites or error handling, leaving some gaps for a complete picture.

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?

The schema has 0% description coverage, so the description must compensate. It explains the 'ids' parameter as a comma-separated list of UIDs from search_pubmed and the 'select' parameter with default '*'. Examples illustrate usage. However, the 'db' parameter is only implied through examples and not explicitly described.

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 document summaries (ESummary) for a list of UIDs from an Entrez database. The verb 'Fetch' and resource 'document summaries' are specific, and the context of 'from an Entrez database' distinguishes it from siblings like fetch_records (full records) and get_full_text (full text).

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 implies when to use the tool: after obtaining UIDs from search_pubmed, as shown in examples. It provides clear context for the input (ids from search_pubmed) and the output (summaries). However, it does not explicitly state when not to use it or compare with alternatives like fetch_records or get_full_text.

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