read_medrxiv_paper

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions downloading/saving PDFs (via save_path) and text extraction, but doesn't cover critical aspects like error handling (e.g., invalid DOI), network dependencies, file system permissions, or performance characteristics (e.g., extraction time). The description doesn't contradict annotations (none exist), but fails to adequately inform about operational behavior.

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 efficiently structured with a clear purpose statement followed by Args/Returns sections. Every sentence adds value, though the 'Args' and 'Returns' labels are slightly redundant with the schema. It's appropriately sized for a tool with two parameters.

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 tool's moderate complexity (PDF processing), no annotations, and an output schema (which covers return type), the description is reasonably complete. It covers purpose, parameters, and return value, but could improve by addressing behavioral aspects like error conditions or dependencies. The presence of an output schema reduces the need to explain returns in the description.

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%, but the description compensates well by explaining both parameters: 'paper_id' is clarified as a 'medRxiv DOI', and 'save_path' specifies the directory purpose and default value. This adds meaningful context beyond the bare schema, though it doesn't detail DOI format requirements or save_path constraints.

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 specific action ('Read and extract text content'), the resource ('from a medRxiv paper PDF'), and distinguishes it from sibling tools like 'download_medrxiv' (which likely downloads without extraction) and 'read_arxiv_paper' (which handles a different source). It goes beyond just restating the name by specifying the extraction functionality.

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 implies usage when text extraction from medRxiv PDFs is needed, but provides no explicit guidance on when to use this tool versus alternatives like 'download_medrxiv' (for just downloading) or other 'read_*' tools for different sources. It lacks any 'when-not-to-use' statements or prerequisites.

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