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

Annotations only say readOnly/idempotent/openWorld; the description adds the parts that actually govern behavior: a $0.003 per-call price, the fact that unauthenticated calls return an x402 request payload rather than data, that a P0 bearer key makes the paid call and deducts the price, and that bad input is refused before any charge. Those are exactly the cost and auth traits an agent needs and that no structured field carries.

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 usage condition and the required inputs are front-loaded, and the pricing/auth details follow in a logical order. It is a single dense run-on sentence carrying a long URL and two distinct execution modes, so it could be broken up, but almost every clause carries real information.

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?

For a paid, open-world lookup with no output schema, the description covers cost, the two calling modes, the auth mechanism, input validation, and where the schema lives. The only soft spot is that 'returns the data' does not say what the verified result looks like, but the paid-request indirection is explained well enough for an agent to act.

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 100%, so tx, to, amount, asset, and chain are all documented in the schema itself, and the description adds no format detail beyond restating three names. Worse, it lists only 'tx, to, amount' while asset is also required and chain is optional, which slightly understates the required input set. Baseline 3 applies.

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 and resource: confirm that a transaction paid at least an amount of an asset to an address. That is far more precise than the sibling evm_transaction or evm_receipt, but it never names those siblings or explains how it differs from them, so the differentiation is left implicit.

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 gives an explicit trigger ('Use when you must confirm that a transaction paid at least an amount of an asset to an address') and even tells the agent which inputs to pass. It does not state when NOT to use it, e.g. when a plain receipt lookup is sufficient, and it offers no explicit routing against the evm_* siblings.

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