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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful domain context: results are limited to preprints that have since been published in a peer-reviewed journal, and medRxiv is included despite the bioRxiv name. It does not describe pagination or result details, but annotations cover the safety profile.

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 a single sentence with no filler and is front-loaded with the core subject. However, it is under-specified rather than usefully concise, omitting usage or parameter guidance that would make it more valuable.

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 0% schema coverage, no output schema, and required parameters, the description is incomplete. It states the data class but leaves the agent to infer invocation details and selection criteria, which is insufficient for confident tool use.

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% and the description says nothing about server, date_or_range, or cursor. The schema itself only provides types and an example, leaving the agent without meaningful parameter semantics. There is no compensation in the description for the low coverage.

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 identifies the resource clearly: bioRxiv/medRxiv preprints that have since been published in a peer-reviewed journal. It conveys a distinguishing criterion, but lacks an explicit verb like 'retrieve' or 'list' and does not explicitly differentiate from siblings such as biorxiv_details or biorxiv_publisher.

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 about when to use this tool versus alternatives like biorxiv_details, biorxiv_publisher, or published. There is no mention of required inputs, exclusions, or conditions that make this tool preferable.

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