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

Annotations already cover read-only/idempotent/open-world safety, but the description adds real behavioral context: default reads retained catalog metadata with observation times, external lookup is capped at two requests with no paper-body reading, and unknown fields (missing DOI, peer review, withdrawal/replacement status) are explicitly disclosed as gaps.

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?

Purpose is front-loaded and every clause carries information, but the single dense block repeats the same ideas ('without research or payment' vs 'before requesting paid research'; 'no paper-body reading' vs 'original paper text is not required'), so it is longer than strictly needed.

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?

With no output schema, the description compensates by describing the return shape (field-scoped bibliography card with provenance, short reference, reusable BibTeX/RIS) and its limitations, plus full parameter coverage via the schema. Nothing needed to call the tool correctly is 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond it by framing searchRepositories as an opt-in external call with a request cap ('at most two requests') and clarifying that language affects only bibliography labels, not preserved titles/authors.

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?

Opens with a specific verb and resource set: 'Find paper titles, recorded contributors, DOI and exact repository versions.' It also implicitly distinguishes itself from the paid 'research'/'research_monthly' siblings by scoping the tool to recorded catalog metadata rather than full-text research.

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?

Gives explicit routing: use it for exact title/author/year/journal/DOI/version questions 'before requesting paid research.' It also constrains the one risky parameter ('Set searchRepositories=true only to explicitly send the query to arXiv/Crossref'), which is a clear when-not rule.

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