Receipts Mint

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the write/open-world nature is covered. The description adds genuinely new behavioral context: the call costs 0.25 USD via x402 in USDC on eip155:8453 — important for an agent that may spend funds. It stops short of disclosing what minting creates, permanence, or replay 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, but short by omission rather than by discipline. The only substantive sentence is a cryptic price/route token string that is not front-loaded with any explanation of the operation.

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?

This is a paid, non-idempotent write tool with 6 undocumented parameters and no required-field guidance. An output schema exists so return values needn't be described, but the description leaves the agent unable to construct a correct call or judge the consequences of making one.

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 (tx, actor, action, subject, metadata, receipt_type) with 0% schema description coverage, yet the description explains none of them. The agent must guess what 'tx' refers to, whether 'metadata' is free-form JSON, or what valid receipt_type values exist.

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 is essentially the name restated ('Receipts Mint') plus the HTTP route POST /v1/receipts/mint. It never says what a receipt is, what minting produces, or how this differs from the numerous receipt/settlement siblings like v1_settlement_receipt or v1_bureau_receipt_check. An agent learns the endpoint but not the purpose.

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 preconditions, and no named alternative among the ~120 siblings. The agent has no basis for choosing this over v1_settlement_receipt, v1_audit_evidence_package, or v1_bio_audit_receipts.

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