fetch_multiple

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

With no annotations, the description bears the burden of describing behavior, and it does by stating the exact return contract: a dictionary mapping each ID to full document text with BibTeX plus abstract. It does not cover invalid-ID/error behavior, but for a read-only fetch operation the disclosed output behavior is substantive.

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?

Three clearly labeled short sections (summary, Args, Returns) with no filler. The precision-step framing is front-loaded and every sentence contributes.

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?

For one required parameter and no output schema, the description supplies the necessary return shape and usage context. However, it refers ambiguously to 'the search tool' when two search-like siblings exist (search and search_reference), and it omits any error or edge-case behavior.

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 only gives 'ids' as a string array, so the description adds the crucial meaning that these are document IDs from previous search results. It does not discuss uniqueness or validity, but this fully compensates for the 0% schema coverage for a single simple parameter.

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 uses a specific verb ('Fetch') and resource ('full documents') and explains this is the precision step after searching, which separates it from search-oriented siblings. It does not explicitly contrast with the sibling 'fetch', so the single-vs-multiple distinction is left implicit.

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?

It gives clear usage context: call this after a search, with IDs from previous search results, to get complete BibTeX records and abstracts. It stops short of explicitly stating when not to use it or naming the alternative for single-document retrieval.

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