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

The description adds important behavior beyond the annotations: cost per call, USDC on Solana payment via x402, the PaymentRequired challenge flow, and the exact _meta key for retry. It does not explain the return value or score semantics, but the payment handshake disclosure is substantial and consistent with the annotations.

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 definition is compact and front-loaded: purpose first, then payment mechanics, then HTTP equivalent. Every sentence carries operational value, and the parenthetical payment retry instruction is dense but necessary.

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?

The description covers invocation and payment clearly, but with no output schema it leaves the return format and score semantics unexplained. It also does not clarify whether 'batch' refers to batch-payment vouchers or batch scoring, which matters because the schema takes a single voucher object.

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?

The single voucher parameter is fully described in the schema, including payer, amount, nonce, expiry, issued_at, and signature. The description adds domain context ('batch-payment vouchers') but no extra syntax, format, or validation guidance beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: score batch-payment vouchers, scoped to settlement risk. This is concrete enough to distinguish it from general scoring or batch tools, and the domain wording tells an agent exactly what the tool evaluates.

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 intended use is implied by 'settlement risk,' but there is no explicit when-to-use, when-not-to-use, or comparison to alternatives such as bridge_score or tokens_score. The payment instructions explain how to invoke it, not when to select it over another tool.

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