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

Annotations only give generic safety hints; the description adds the critical paid-call behavior: 0.50 USDC on Base over x402, no Agoreum account, first call returns PaymentRequired as isError, second call carries signed payment in _meta, settlement appears in _meta, and no charge occurs if checks fail. This is exactly the behavioral context an agent needs for a paid tool.

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?

Dense but well front-loaded: purpose first, then usage, then payment mechanics, then a pointer to list_agoreum_tools. It is longer than typical because the x402 payment flow genuinely needs explanation, though the final pointer sentence is the least essential.

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 no output schema and a non-trivial paid x402 workflow, the description covers what the tool returns (feedback file and wallet call), how payment is handled, and what happens on failure. An agent can call it correctly from this description alone.

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 schema already documents every parameter with constraints. The description restates the key inputs (tx_hash, agent_id, score) and notes the return value, but does not add parameter-level detail beyond what the schema provides.

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?

States a specific verb chain (checks payment, builds ERC-8004 feedback file) and the artifact produced, ready for the wallet to send. It is clearly distinguishable from sibling check_usdc_payment because the output is a feedback file rather than a verification result.

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?

Explicitly says to use it after paying an agent to leave ERC-8004 feedback carrying proof of payment, and gives the exact two-call x402 workflow including the no-payment terms call. This leaves little ambiguity about when and how to invoke it.

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