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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that this writes to the filesystem (via save_path), what the return value contains (file path, binary data, or status), error conditions (invalid paper_id, network failures), or whether operations are idempotent.

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 single-sentence description is appropriately front-loaded with the core action and wastes no words. However, given the complete lack of schema descriptions and annotations, extreme brevity becomes a liability rather than a virtue.

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 tool with zero schema descriptions, no annotations, and no output schema, the description is insufficient. It omits critical context including parameter details, side effects (filesystem mutation), return value structure, and error handling that the agent needs to invoke the tool correctly.

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%, requiring the description to compensate. While 'paper_id' is implicitly understood as the paper identifier, the description does not explain the expected format (numeric ID, URL, etc.) or that 'save_path' determines the local directory for the downloaded file.

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 action ('Download'), format ('PDF'), and resource ('IACR ePrint paper'). It implicitly distinguishes from sibling 'read_iacr_paper' by specifying 'Download PDF' versus reading content, and from other download_* tools by naming the specific source 'IACR ePrint'.

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 explicit guidance on when to use this tool versus alternatives like 'read_iacr_paper' (text extraction) or 'search_iacr' (discovery). While 'PDF' hints at file retrieval versus content parsing, explicit when-to-use guidance is absent despite clear functional siblings.

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