paper_batch_download

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

With no annotations provided, the description carries full burden and discloses key behavioral traits: sequential processing, 1-50 max limit, 2s delay, source prioritization (open access before Sci-Hub), and output format (markdown summary). It does not cover error handling or authentication needs, but provides substantial operational context.

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 front-loaded with core functionality, followed by structured sections for args, returns, and examples. Every sentence earns its place: the first sentence defines purpose and constraints, subsequent sections efficiently document usage 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's moderate complexity (batch download with constraints), no annotations, and an output schema present (so return values need not be explained), the description is complete. It covers purpose, usage, parameters, behavior, and examples, providing sufficient context for an agent 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 description coverage is 0%, so the description must compensate. It explains both parameters: 'identifiers' as a list of DOIs, arXiv IDs, or URLs, and 'output_dir' as a save directory with default. This adds meaningful semantics beyond the bare schema, though it could detail format constraints for identifiers.

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 verb 'download' and resource 'multiple papers' with specific scope 'sequentially (1-50 max, 2s delay)'. It distinguishes from sibling tools by specifying batch processing versus paper_download (likely single) and paper_metadata (information 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 provides clear context for when to use this tool: for downloading multiple papers (1-50) with a delay. It implies an alternative to paper_download for batch operations but does not explicitly state when-not-to-use or compare with paper_metadata. The prioritization of sources offers some guidance on behavior.

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