download_biorxiv

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

With no annotations provided, the description carries full burden. It states the tool downloads a PDF and returns a file path, but doesn't disclose important behavioral traits like network dependencies, error handling (what happens if paper_id is invalid), authentication requirements, rate limits, or whether it creates directories if save_path doesn't exist.

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 perfectly structured and front-loaded: first sentence states the core purpose, followed by clearly labeled sections for Args and Returns. Every sentence earns its place with zero waste or 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 has an output schema (which covers return values) and relatively simple parameters, the description is adequate but incomplete. It covers the basic operation but lacks important context about behavioral traits (network operations, error conditions) that would be needed for robust agent usage, especially with no annotations.

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 provides meaningful context for both parameters: 'paper_id' is explained as a 'bioRxiv DOI' (not just any string), and 'save_path' gets a default value explanation and purpose clarification. This adds significant value beyond the bare schema.

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 specific action ('Download PDF'), target resource ('bioRxiv paper'), and distinguishes it from siblings by specifying the source (bioRxiv vs. arXiv, medRxiv, etc.). It's a precise verb+resource combination that differentiates this tool from other download tools in the list.

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 'download_medrxiv', 'download_arxiv', or the sibling 'read_biorxiv_paper' tool. It mentions the required parameter but doesn't explain context or prerequisites for usage.

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