Cited retrieval from the official biosafety-guidance corpus (PAID $0.50)

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

The description adds genuinely useful information beyond the annotations: the exact price ($0.50) and the payment rail (x402/base/usdc on eip155:8453), plus the remote route. It does not explain why a retrieval endpoint is annotated readOnlyHint=false (presumably because of the charge), nor whether payment failure, retries, or double-charging are concerns given idempotentHint=false.

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?

It is short and front-loaded, which is good, but the first sentence duplicates the title verbatim and the second is pure transport metadata. Every sentence is compact, yet the space is spent on restatement rather than on the parameter and payment-flow information that is actually missing.

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 explained. Still, for a paid, non-idempotent, open-world tool with six undescribed parameters, the definition leaves critical operator questions unanswered (cost triggering, payment flow, parameter semantics).

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?

Six parameters with 0% schema description coverage, and the description mentions none of them. Non-obvious ones like as_of (format? date? version?), compare (what is being compared, max 2 items?), and source_ids are entirely undocumented, so an agent must guess at semantics.

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?

It names a specific resource (the official biosafety-guidance corpus) and a specific mode (cited retrieval), which is more than a restatement of the name. However, it gives no signal distinguishing it from near-neighbours such as v1_bio_catalogue, v1_compliance_check, or v1_evidence_query, so an agent cannot route confidently on purpose alone.

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?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. With ~120 siblings, several of which sound like compliance/evidence lookups, the absence of any routing guidance is a real gap.

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