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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint. The description adds meaningful behavioral context by stating 'deterministic replay' and emphasizing that supplier payment is not executed, which clarifies the read-only nature beyond the raw annotations. No contradiction is present.

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 description is compact and front-loaded, with the core scope stated first and the non-execution clarification in the second sentence. It has no filler, though some terms like 'Paid RunOnProof' and 'Proof Capsule' are jargon-heavy for an agent without prior context.

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?

Given the high complexity of a 24-parameter, all-required tool with only 4% schema coverage, the description is too thin. It does not explain the release-payment decision workflow, the meaning of 'deterministic replay' for the caller, or how the many nested objects fit together. The output schema exists, but that does not compensate for the missing input-semantics context for an agent selecting among many sibling tools.

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 only 4%, so the tool description carries the responsibility for explaining 24 required parameters. It mentions concrete artifacts like signed BuyerPaymentMandate and signed Proof Capsule, and gives example values (US, FEDERAL_ONLY, 0.79 USDC, Base), but it does not explain the meaning or purpose of most parameters such as idempotency_key, risk_policy, or evidence_references.

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 specifically identifies a US FEDERAL_ONLY release-payment decision for 0.79 USDC on Base, with signed BuyerPaymentMandate and Proof Capsule, and explicitly states that supplier payment is not executed. This makes the tool's role clear and distinguishes it from payment-execution siblings like authorize_payment.

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 description implies use for US federal-only payment decisions and clarifies that RunOnProof does not execute the supplier payment. However, it does not explicitly state when to prefer this tool over siblings or mention exclusions, leaving the routing decision mostly to inference.

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