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

The description discloses paid execution ('Price: $0.50 via x402'), the challenge-then-signature flow, and the at-most-once retry contract enabled by a stable _salt19_operation_id. This goes beyond the annotations' idempotentHint=true by explaining how to actually achieve idempotency, though it does not fully describe payment-side effects.

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?

Core behavior is stated first in a single sentence, followed by a compact payment and retry note. There is slight redundancy between 'preserve it across retries' and 'A stable _salt19_operation_id is required and makes semantic retries at-most-once,' but the overall description is efficient and front-loaded.

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?

With an output schema present and annotations covering idempotency and non-destructiveness, the description covers the key operational requirements: cost, challenge/signature order, and retry semantics. Missing use-case differentiation and fuller semantics for context and required_standard are minor gaps that do not block a competent agent.

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 coverage is 100%, so the baseline is 3. The description adds real semantics for _salt19_operation_id and _x402_payment_signature, but claim, context, evidence, required_standard, and _salt19_handoff_id remain only generically described in the schema itself.

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 opens with a specific verb ('Map') and a clear resource ('an autonomous agent claim or output to supplied evidence'), then enumerates the exact verdicts returned. This makes the tool's purpose unmistakable and distinguishes it from generic verifier siblings like agent-plan-verifier, even without naming them.

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?

It provides clear operational context for x402 payment and idempotent retries, and implies use when you have a claim and evidence to assess. However, it never states when to prefer this over agent-plan-verifier, verify-decision-receipt, or other verification tools, nor does it list exclusions or alternative conditions.

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