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

Goes well beyond annotations by disclosing the $0.01 USDC on Solana cost model, that the paid report contains the verdict plus per-field comparison and register record, and that submitted content is processed in memory only and never stored. The non-idempotency announced in annotations is only obliquely supported ('the paid retry re-sends the reference'), and the interplay between the 100/day free allowance and the per-call price is left slightly ambiguous.

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 opening repeats the price twice ('$0.01 USDC on Solana — $0.01 buys...') and the actual verification semantics arrives only in the fourth sentence, after pricing and data-handling text. Content is mostly useful, but the front-loading favors price over function.

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 correctly compensates by enumerating what the paid report contains (verdict, per-field comparison, register record) and what it does not do. For a two-parameter tool with full schema coverage and annotations, this is close to sufficient; only the precheck relationship and free-tier mechanics remain underspecified.

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% and both parameters are already well documented there, including the reference shape and the wallet-keyed allowance. The description adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource: verifies that a submitted citation reference resolves in its register and whether the claimed fields match. It also clearly bounds the purpose with exclusions (does not judge support for claims, does not grade the work). It stops short of naming sibling refcheck_precheck/refcheck_criteria, so an agent must infer the relationship from 'the paid retry'.

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 price and the free-allowance concept (100/day per wallet, in the schema) imply this is the paid call, and 'the paid retry re-sends the reference' hints at a separate precheck path, but the description never says when to call this versus refcheck_precheck or refcheck_criteria. Usage is implied rather than stated.

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