download_iacr

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

Despite no annotations, the description notes 'always free' and alludes to saving to disk. However, it does not disclose potential behaviors like overwriting existing files, required permissions, or error handling.

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 brief and front-loaded, with a separate args/returns/example section. It is efficient but could benefit from a more structured format like bullet points.

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 output schema, the description includes return type. However, it lacks details on file naming behavior, overwriting policy, or error scenarios, which are important for completeness.

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?

With 0% schema description coverage, the description compensates by explaining the 'paper_id' format with an example ('2024/123') and clarifying that 'save_path' is a directory for saving. This adds meaning beyond the 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 it downloads PDF from IACR ePrint, distinguishing it from other download tools. The phrase 'always free' adds useful context.

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?

Provides an example usage but lacks explicit guidance on when to use this tool versus other download tools (e.g., download_arxiv). No mention of prerequisites or exclusions.

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