x402 Bureau — conformance-check any issuer's receipt/offer (PAID $0.05)

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

Annotations are fairly rich (readOnlyHint=false, openWorldHint=true, idempotentHint=false), so the safety profile is mostly covered. The description adds genuinely useful, non-annotation context: the paid price, the remote route (POST /v1/bureau/receipt-check), and the payment rail (0.05 USD x402 on eip155:8453). It does not explain what state is affected by the non-read-only call or how payment failure behaves.

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 text is short and front-loaded, which is good, but the first line is a verbatim restatement of the title, so roughly half the description is redundant. The route/payment line is the only net-new content.

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. But for a paid, open-world call taking two free-form nested objects, the description gives no guidance on input shape, expected conformance criteria, or cost/authorization behavior on failure — leaving significant gaps for a relatively complex tool.

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% and both parameters are open nested objects (additionalProperties: true) with no structure documented. The description says nothing about what an 'offer' or 'receipt' should contain or which fields are inspected, leaving the agent unable to construct valid input from the definition alone.

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 gives a specific verb+resource: 'conformance-check any issuer's receipt/offer'. An agent can understand the operation without opening the schema. However, it offers no differentiation from the many similar siblings (v1_bureau_audit, v1_bureau_reputation, v1_payment_envelope_validate, v1_receipts_mint), so the agent cannot tell which bureau-style tool to pick.

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 when-to-use guidance, no prerequisites, and no named alternatives. The only implicit signal is 'PAID $0.05', which hints at a commercial check but does not state when an agent should choose this over v1_payment_envelope_validate or v1_bureau_audit.

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