read_biorxiv_paper

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

No annotations provided; description implies read operation but mentions saving a PDF, suggesting potential download. However, it does not disclose side effects (e.g., network access, file system writes) or behavior when the PDF is not found. Important behavioral context is missing.

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 compact and well-structured, with a clear purpose statement followed by an Args/Returns format. Every sentence adds value without redundancy.

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?

Covers the basics: purpose, parameters, return type. However, lacks error handling details, prerequisites, and deeper behavioral context (e.g., does it require an internet connection?). Given no annotations and simple output, it is adequate but not thorough.

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 meaning beyond the schema by clarifying that paper_id is a 'bioRxiv DOI' and that save_path is a directory where the PDF is saved (with default './downloads'). Schema coverage was 0%, so this addition is valuable.

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'), the resource ('bioRxiv paper PDF'), and the output ('text content'). It distinguishes from sibling read tools by specifying the source as bioRxiv.

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?

No explicit guidance on when to use this tool versus alternatives like download_biorxiv or other read_*_paper tools. The description simply states what it does without contextualizing its appropriate use cases.

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