read_medrxiv_paper

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions extracting text from a PDF and implies downloading via the save_path parameter, but it does not clarify side effects (e.g., file persistence), rate limits, or what happens if the PDF is already cached. The description is insufficient for a tool with no annotations.

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 extremely concise: a single sentence for the purpose, followed by a clean Args/Returns block. Every element is necessary and no filler exists. The structure makes it easy for an AI agent to parse quickly.

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 simplicity (two parameters, no nested objects), the description covers the core functionality and parameter semantics. It does not address error handling or edge cases, but the contextual signals (output schema exists) and sibling tools provide enough context. A 5 would require some mention of typical error scenarios or limitations.

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 schema itself has no descriptions for parameters (0% coverage). The description compensates by explaining that paper_id is a medRxiv DOI and save_path is a directory for saving the PDF. This adds valuable semantic meaning beyond the schema's type-only fields.

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 tool's purpose: 'Read and extract text content from a medRxiv paper PDF.' The verb 'read' and resource 'medRxiv paper PDF' are specific, and the tool is well-differentiated from sibling tools such as read_arxiv_paper or read_biorxiv_paper by the source name.

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 implicitly indicates that this tool is for reading medRxiv papers via a DOI. While it does not explicitly list when not to use it or mention alternatives, the context of sibling tools makes the usage clear. A higher score would require explicit guidance on when to choose this over other read_*_paper tools.

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