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

Annotations already declare this a safe, idempotent, open-world read, so the bar is lower. The description still adds non-obvious context: the results cover both submissions and publications, and the endpoint does not exist for medRxiv, which prevents wasted calls on an unsupported preprint server.

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?

Three short, front-loaded clauses with no filler; the output type comes first, followed by the parameter, then the scope caveat. The only minor waste is repeating the interval values already present in the schema.

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 zero-required-parameter count tool with a full output schema and complete annotation coverage, the description covers purpose, parameter values, and repository scope. The remaining gap is routing relative to sibling bioRxiv tools, which the description never addresses.

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 coverage is 100% and the description simply restates the interval enum ('m' monthly default or 'y' yearly) verbatim from the schema. It adds no meaning beyond what the schema already documents, so the baseline of 3 applies.

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 names a concrete resource and output ('bioRxiv submission/publication counts'), which is more specific than the title 'Biorxiv Summary'. It does not, however, distinguish this tool from bioRxiv siblings such as biorxiv_details or biorxiv_published, which an agent must choose between.

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?

Usage is only implied: the tool returns aggregate counts, and the note 'bioRxiv only — medRxiv has no /sum endpoint' scopes it to one repository. No alternative tool is named and there is no explicit when-to-use versus when-not-to-use guidance.

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