read_iacr_paper

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

No annotations are provided, so the description must bear the burden. It discloses that it extracts text and mentions a save_path implying possible download behavior, but does not clarify if it modifies state, requires auth, or has rate limits.

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 structured with a clear first sentence and Args/Returns sections. It is not overly long but could be more concise by removing the technical Args list formatting.

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 the existence of an output schema (not shown) and the tool's complexity, the description covers basic functionality and parameters. However, it does not specify prerequisites (e.g., whether the PDF must be downloaded first via download_iacr) or edge cases.

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 adds meaning: paper_id is an IACR ID with example '2009/101', and save_path is the directory. This largely compensates for the schema gap, though paper_id format could be more precise.

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 verb 'Read and extract text content' and the specific resource 'IACR ePrint paper PDF', which directly distinguishes it from sibling read_*_paper tools targeting other sources.

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 guidance on when to use this tool vs alternatives like read_arxiv_paper or when to first use download_iacr. Given the many similar siblings, explicit usage context is missing.

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