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

Annotations declare read-only, open-world, and idempotent behavior, but the description does not explain return format, pagination via the cursor parameter, or how the date range and server parameters affect results. The 'subsequently published' behavior is only vaguely conveyed.

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, concise sentence with an illustrative example. It avoids unnecessary words and is easy to read.

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?

Without parameter details, output schema, or usage guidance, the tool description is incomplete for an agent to invoke it correctly. The basic intent is clear, but key operational aspects are missing.

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?

Only the 'prefix' parameter receives a description; the required 'server' and 'date_or_range' parameters and the optional 'cursor' parameter are unexplained. With 25% schema coverage, the description fails to compensate for the missing parameter meanings.

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 indicates the tool retrieves bioRxiv/medRxiv preprints that were subsequently published under a given DOI prefix, with the example aiding comprehension. However, it lacks an explicit verb like 'list' or 'search', and the relationship to sibling tools such as biorxiv_published is not addressed.

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 instead of alternatives like biorxiv_published, published, or publisher. The description does not mention scenarios, prerequisites, or distinctions from sibling tools.

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