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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: metadata provenance from Crossref (real publisher records, not generated text) and a per-call volume limit. The only blemish is that the stated 'up to 50 DOIs' does not match the schema's maxItems of 60, which could confuse an agent about the true cap.

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?

Four tight sentences, front-loaded with the trigger condition, then outputs, then provenance, then limits and exclusions. No filler and no repetition of 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?

An output schema exists, so return values need not be spelled out, yet the description still names the export formats and their target managers (Zotero, EndNote, Mendeley). For a two-parameter read-only tool, an agent has everything needed to call it correctly.

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 both parameters are already documented, including the style enum and the DOI array format. The description adds little beyond restating the style options and a volume limit that conflicts with the schema's maxItems. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource (format a bibliography from DOIs), names the four supported styles, and names the concrete artifacts produced (APA/MLA/Chicago/IEEE reference list plus BibTeX and RIS files). This is clearly distinguishable from the sibling tools find_papers and get_paper_network, which retrieve rather than format.

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?

Opens with an explicit trigger condition ('when the user has a list of DOIs and wants a reference list') and then states exclusions: no titles, no web page URLs, no citation text, and no manuscript checking. That combination of when-to-use plus when-not-to-use is exactly what routes an agent correctly.

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