Signed BioAudit receipt for an administrative biosecurity check (PAID $0.25)

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the agent knows this is a non-idempotent write. The description adds genuinely new behavioral context — the x402 payment of 0.25 USDC on eip155:8453 and the POST route — but never warns that a non-idempotent paid call means retries cost money and may produce duplicate receipts, nor what the payload's seven inputs are for.

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 a verbatim restatement of the title and the second is a terse route/price string, so effectively only one new fact is conveyed. No waste in length, but little is earned per sentence.

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?

For a paid, non-idempotent mutation tool with seven undocumented inputs and a nested free-form object, the description omits what the seven fields mean, which are needed, and what a receipt represents. The presence of an output schema relieves it of describing return values, but the input-side gaps are substantial.

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 0% across seven parameters (subject, check_type, requested_at, policy_version, service_version, outcome_category, and a free-form nested 'inputs' object), and the description mentions none of them. With coverage this low the description carries the burden of explaining parameter meaning, and it does nothing here.

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 names the resource (a signed BioAudit receipt for an administrative biosecurity check) and its price, but it is a noun phrase with no verb — an agent cannot tell from the text whether this mints a new receipt or fetches an existing signed one. The name partially differentiates it from the sibling v1_bio_audit_verify, but the description itself does not state the distinction.

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 call this versus v1_bio_audit_verify, v1_receipts_mint, or v1_bio_verification_checks. The only usage-adjacent signal is the $0.25 cost, which implies a paid prerequisite but gives no conditions or exclusions.

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