download_iacr

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

No annotations are provided, so the description must carry the burden. It only states 'Download PDF' and returns a path, but it does not disclose behavioral traits such as whether it is idempotent, if it overwrites files, or any network dependencies. Minimal disclosure.

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 short and structured: a clear one-line summary, followed by bullet-style args and returns. Every sentence is necessary and easy to parse.

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 no annotations and a simple download operation, the description is largely complete. It mentions the return path but could be improved by noting file naming behavior or error handling. Output schema exists but is not shown here.

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 beyond the input schema by explaining the purpose of both parameters (paper_id with example, save_path with default explanation). Schema coverage is 0%, so this compensation is critical.

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 explicitly states 'Download PDF of an IACR ePrint paper,' which is a specific verb+resource combination. It clearly distinguishes itself from sibling tools that download from other sources (e.g., download_arxiv) or perform read/search operations.

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 the tool's purpose but does not give explicit guidance on when to use it versus alternatives. The context implies it is for IACR papers, but no exclusions or when-not-to-use conditions are stated.

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