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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'look up' which implies a read operation, but it does not disclose important traits such as maximum batch size, handling of invalid IDs, rate limits, or the structure of the returned data. This is insufficient for a batch operation.

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 a single concise sentence that directly states the tool's function without any wasted words. It is front-loaded and appropriately sized for a simple operation.

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 a batch lookup tool with no output schema and no annotations, the description is too sparse. It does not mention return format, batch limits, or error behavior, leaving significant gaps for an agent to invoke the tool correctly. The parameter is well-documented, but the operation-level context is lacking.

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 input schema fully documents the single parameter 'paperIds' with a clear description ('Array of paper IDs (Semantic Scholar IDs, arXiv IDs, DOIs, etc.)'). The tool description adds no additional parameter meaning, so the baseline of 3 applies due to high schema coverage.

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 'Look up multiple papers by their IDs' uses a specific verb ('look up') and resource ('multiple papers'), clearly distinguishing this batch operation from single-paper lookup or search siblings. The phrase 'by their IDs' specifies the input method, making the tool's function 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?

The description provides no guidance on when to use this tool versus alternatives like get_paper_details or search_papers. There is no mention of when batch lookup is appropriate, nor any exclusions or prerequisites. The implied usage is minimal and not explicitly stated.

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