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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds materially more: ordering (newest first), result semantics (worked/not plus plain error name), and a concrete cost/payment model (25 free calls/day, then $0.01 USDC per call via x402). The "mainnet-beta (real money)" warning is a genuinely useful operational caveat.

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 opening sentences are well front-loaded and high value, but the "Inputs:" section duplicates a 100%-covered schema nearly verbatim, and the docs pointer plus cost line stretch a definition that could make its point in half the words.

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?

There is no output schema, and the description compensates by describing what comes back (latest transactions, success status, plain error name). Cost, network risk, and the tx-ID sourcing use case are all covered; only pagination/limit behavior beyond the schema's max=50 and the docs URL's contents are left implicit.

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 the schema already documents wallet, network, and how_many including defaults, enum values, and the "not a .sol name" caveat. The description's Inputs block largely restates this, adding the "real money" framing but no syntax or format detail the schema lacks.

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+resource ("Lists a wallet's latest transactions, newest first") and even describes the return shape (success flag plus plain error name). An agent can distinguish this from siblings like check_tx, why_failed, and explain_tx, which operate on an already-known transaction.

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?

Gives a clear triggering condition ("Run to see a wallet's recent activity, or to get a real transaction ID to look into") and an important prohibition ("Never make up a transaction ID; get one here"). It never names specific alternatives such as check_tx or why_failed, so the routing is implied rather than explicit.

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