batch_get_papersRetrieve details for multiple academic papers at once from a list of paper IDs, so you can gather metadata for several references in a single call.
Retrieve details for multiple papers at once.
paper_ids: List of paper IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| paper_ids | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic retrieval action and does not disclose return format, pagination, error handling, rate limits, or whether partial results are possible.
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 lines, front-loaded with purpose. The bullet restating paper_ids is redundant with the schema, so not every sentence earns its place, but the description is not verbose.
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 retrieval tool with no annotations and no output schema, the description is too sparse. It omits batch limits, error behavior, and return structure that an agent would need to invoke it correctly.
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 0% and the description merely restates the parameter name as 'List of paper IDs', adding no format, constraints, or batch size limits beyond what the schema already provides.
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?
States a specific verb 'Retrieve' and resource 'details for multiple papers', with 'at once' indicating batch scope. It distinguishes itself from single-paper siblings like get_paper_details, but does not name alternatives explicitly.
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?
Implies usage when multiple paper IDs are available, but gives no explicit when-not or alternative routing (e.g., use get_paper_details for a single paper). No prerequisites or context about when batch retrieval is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.