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 but fails to specify critical details such as whether the operation overwrites existing files, what the function returns (file path, binary content, or status), or error handling 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 extremely brief (6 words) and front-loaded with the action verb, avoiding unnecessary prose. However, given the undocumented parameters and behavioral gaps, it is underspecified rather than optimally concise.

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 tool with file system side effects and two parameters lacking schema descriptions, the description is incomplete. It omits the default save_path value, return value specification, and distinctions between this tool and the 'read' variant.

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 has 0% description coverage for its 2 parameters. While 'bioRxiv paper' provides minimal context for paper_id, the description does not compensate for the lack of schema documentation by clarifying the expected ID format (DOI vs bioRxiv ID) or save_path behavior (directory vs filename).

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 (Download PDF) and target resource (bioRxiv paper), effectively distinguishing it from sibling tools like 'read_biorxiv_paper' and download tools for other repositories (arxiv, medrxiv, etc.).

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 versus the 'read_biorxiv_paper' alternative or other sibling tools, nor does it specify prerequisites such as the required format for the paper_id parameter.

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