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

The description discloses several behavioral traits: no LLM involvement, every claim carries source and retrieval time, byte-reproducible JSON, and a 3-reference limit. However, it contradicts itself by describing the output as 'signed (Ed25519...)' and then declaring it 'unsigned'; it also says 'For every reference' then limits to the first 3. These inconsistencies undermine trust in the description's accuracy.

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 dense single block of semicolon-separated clauses rather than a well-structured, front-loaded summary. It contains valuable information but is hard to parse quickly and includes redundant or contradictory statements. A bulleted list or clearer separation of caveats would improve it.

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?

There is no output schema, so the description's mention of the JSON report contents and per-reference checks is helpful. It also covers input types and the preview limitation. Yet the signed/unsigned contradiction and the lack of explanation for the options parameter leave meaningful gaps for an agent deciding how to invoke the tool 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 67%, so the schema already documents bibtex and references well. The description adds that input can be structured references or BibTeX, which matches those parameters, but it provides no additional detail about the 'options' object or how the booleans behave. This is adequate but not compensating beyond the schema.

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 states the tool verifies a bibliography and enumerates the checks performed for each reference (existence, resolution, retraction/correction, metadata match, fabrication risk). It distinguishes itself as a free preview limited to 3 references, which separates it from the sibling citation_report tools. However, the output description is confusing because it first says 'signed' then later says 'unsigned', muddying what exact artifact is produced.

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?

The description conveys when this tool is appropriate: it is a free preview, checks only the first 3 references, is unsigned, and requires no payment. This implies a limited trial use case and distinguishes it from paid/full-report siblings. It does not explicitly name alternatives like citation_report, but the preview limitation is an adequate usage signal.

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