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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely non-redundant behavior: the upstream source (Crossref publisher records, Unpaywall for OA), the 30-works-per-call ceiling, and a negative-capability clause (no summarizing, no full-text reading, no quality judgement) that prevents misuse. It stops short of noting result freshness, ranking caveats, or what the returned bibliography file contains.

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 sentences, each doing distinct work: capability and output, then mechanics and return ceiling, then explicit exclusions. The use case and the sibling routing are front-loaded, and no sentence is filler or restates the title.

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 read-only search tool with a full schema and an output schema, the description covers everything an agent needs to call it correctly: what it searches, what the results include, the 30-item cap, and the three things it will not do. Return-value structure is legitimately omitted because the output schema exists.

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 100%, so all seven parameters including enums, ranges and defaults are already documented in the schema. The description restates the filter set (year range, minimum citations, open-access filter, sort) and adds only the minor provenance detail that the OA filter is backed by Unpaywall. With the schema doing the heavy lifting, 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 specific verb and resource ("literature list or reading list on a research topic") and immediately enumerates what the result carries: real citation counts, open-access links, and a bibliography file. It also explicitly disambiguates from both siblings by name, so an agent can route correctly without opening any schema.

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?

It gives both positive and negative routing conditions: use when the user wants a topic-based reading list, do not use for a single known paper (route to get_paper_network) or for formatting known DOIs (route to format_bibliography). Both alternatives are named with the condition that selects them, leaving nothing to inference.

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