The BioTrust service catalogue an agent routes from (PAID $0.02)

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower, and the description adds genuinely new context the annotations cannot carry: the exact remote route (GET /v1/bio/catalogue), that the call is PAID, the price of 0.02 USD, and the settlement rail (x402/base/usdc on eip155:8453). This cost/payment disclosure is material for an agent deciding whether and how to invoke it. It stops short of noting whether the charge applies per-call or per-retry, or any failure/refund behavior.

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, but the first line is an exact restatement of the title, which is pure duplication rather than added information. The one substantive sentence (remote route plus payment rail) carries the whole payload, so structure is acceptable but the opening is wasted.

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 needn't be described, and the price/rail disclosure covers the main cost concern. What is missing is what the catalogue actually contains and how it relates to the surrounding BioTrust tools — for a routing/discovery tool with many similar siblings, that gap matters.

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 nominally 100%, so the baseline of 3 applies, but the schema text is tautological ('Query parameter `service_id`.') and the description adds nothing about what service_id filters on, or what include_schemas / include_limitations toggle. The description neither compensates for the low-quality schema text nor makes any parameter claim.

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 identifies the resource (a BioTrust service catalogue) and implies the operation (reading/routing from it), and the 'v1_bio_*' prefix plus the resource name distinguishes it from most siblings. However, the phrasing is a noun phrase lifted verbatim from the title rather than a clear verb+resource statement, so an agent must infer that this is a listing/retrieval call.

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 clause 'an agent routes from' is the only usage hint, suggesting it belongs in a routing/discovery step before calling a specific BioTrust service. There is no explicit when-to-use, no when-not-to-use, and no naming of alternatives among the many bio_* siblings (v1_bio_trust_providers, v1_bio_workflows, v1_bio_verification_checks, etc.), leaving selection to guesswork.

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