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

The description frames this purely as an informational query ('Check whether...'), which implies a safe, idempotent read, while the annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false. That is a direct conflict between the described behavior and the structured safety profile. Per the rubric, a description that contradicts annotations scores 1.

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?

Four tight sentences, front-loaded with the core purpose, then the RPC strategy and the credit/refund policy. Every sentence carries information, though 'using two independent RPCs' and the payment-assumption note could be tightened slightly.

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?

An output schema exists, so return values need no explanation, and the description usefully adds the cost and the refund-on-quorum-failure policy plus the independence of the two RPCs. The one real gap is that it never acknowledges the destructive/credits-spending safety profile the annotations claim.

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 0%, so the description does not compensate for the single parameter, and it says nothing about txHash (e.g. that it must be a Base Mainnet hash). The only format guidance comes from the schema's regex pattern, which is quite self-documenting, so a baseline 3 is fair.

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 concrete verb and resource ('Check whether a Base Mainnet transaction...') and enumerates the possible outcome states (not found, confirmed, safe, failed). The clause 'No payment assumptions are made' implicitly distinguishes it from payment-verification siblings such as verify_usdc_payment. It never names a sibling explicitly, so it stops short of a 5.

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?

Usage is implied: check a Base transaction's status, and the 'no payment assumptions' note suggests it is the non-payment counterpart to verify_usdc_payment. However, there is no explicit when-to-use / when-not-to-use statement and no named alternative, so the agent must infer routing.

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