fetch_batch

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

With no annotations, the description carries the burden of behavioral disclosure. It states that the tool returns structured data per PMID and explains the effect of include_abstract=false with an example. This covers the core behavior, though it does not mention error handling or rate limits.

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 sentences, front-loaded with the main purpose, followed by a relevant parameter tip. No redundant wording or filler.

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's simplicity (2 params, no output schema or annotations), the description is mostly complete: it explains the batch behavior, the return shape, and the optional flag. It could be slightly more explicit about output field details or potential limitations, but overall sufficient for a straightforward fetch tool.

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 parameters are already documented. The description adds value by clarifying the batch context for 'pmids' and providing a use-case example for 'include_abstract' beyond the schema's default-value explanation.

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 'Retrieve abstracts for multiple PMIDs in a single batch request' with a specific verb, resource, and scope. It distinguishes itself from siblings like 'fetch' (single-PMID) and 'get_full_text' by specifying batch abstract retrieval.

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 the primary use case (multiple PMIDs) and provides a concrete guideline for setting include_abstract=false when only full author lists are needed. However, it does not explicitly contrast with siblings like 'fetch' or 'batch_process'.

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