download_medrxiv

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

With no annotations provided, the description must fully convey behavioral traits. It states the return value (path to downloaded PDF) but omits potential failure modes, authentication needs, or side effects. The description is adequate but lacks depth for a tool with no annotations.

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 concise, starting with the core purpose, then listing arguments in a clear format, and finally stating the return value. Every sentence serves a purpose with no extraneous information.

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 simple download tool with no output schema and minimal schema coverage, the description covers the main inputs and output. It does not explain error handling or edge cases, but for its intended use, it is sufficiently complete. Slight improvement could be made by noting required parameters.

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?

Given 0% schema coverage, the description compensates well by explaining paper_id as a medRxiv DOI with an example and save_path as a directory to save PDF. This adds meaningful context beyond the schema's type definitions, though the optional nature of save_path is not explicitly clarified.

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 'Download PDF from medRxiv' which identifies the specific verb (download) and resource (PDF from medRxiv). It also notes it's free and open access, distinguishing it from potentially paywalled sources among sibling tools like download_pubmed.

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 implies when to use (when needing to download a PDF from medRxiv) and gives an example DOI format, but does not explicitly state when not to use or mention alternative tools like read_medrxiv_paper for viewing abstracts. Usage context is implicit.

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