read_medrxiv_paper

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 mentions downloading and extracting but does not indicate whether the operation is read-only, idempotent, or requires internet access. The side effect of saving a PDF (via save_path) is implied but not explained in terms of local modification.

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, using a clear Args/Returns structure that is well-organized and front-loaded. Every sentence provides essential information 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?

For a simple tool with two parameters and no output schema, the description covers the core purpose and parameters. However, it lacks usage context, behavioral details, and error handling information. It is minimally viable but has clear gaps given the absence of annotations.

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 coverage is 0%, but the description adds meaningful context: it specifies that paper_id is a medRxiv DOI and save_path is a directory for saving the PDF. This adds value over the bare schema titles. However, the optionality and default behavior of save_path are not clarified.

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 downloads and extracts full text from medRxiv papers, with a specific verb and resource. It distinguishes from sibling tools like download_medrxiv (which likely only downloads PDF) by explicitly including extraction to Markdown.

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 guidance is provided on when to use this tool versus alternatives such as download_medrxiv or other read_* tools. There is no mention of prerequisites, context, or conditions that would help an agent decide to use this tool.

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