download_paper

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

The description discloses the key behavior of caching (skip redownload if already saved) and that it returns a path. Since no annotations are provided, this adds helpful context beyond the schema.

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 with two short paragraphs, front-loading the main purpose and caching behavior, followed by parameter details. No redundant sentences.

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 one-parameter tool, the description covers the main functionality and parameter details adequately. It does not explain the output schema, but that is acceptable as per guidelines since an output schema exists.

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 description adds significant meaning to the single parameter 'paper_id' by providing an example format, noting that prefixes like 'ARXIV:' and version suffixes are allowed. This compensates for 0% schema description 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 clearly states it downloads arXiv paper PDFs to local storage and returns the file path. It distinguishes itself from siblings like 'read_paper' by focusing on downloading rather than reading or displaying.

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 a local PDF) and mentions caching behavior, but it does not explicitly state when not to use or contrast with sibling tools like 'get_paper_by_id' or 'read_paper'.

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