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

Annotations already mark this read-only, idempotent and non-destructive; the description adds genuinely new context: newest-first ordering, per-transaction success status, plain-name error reporting, and a concrete cost model (25 free calls/day, then $0.01 USDC per call via x402). Pagination behavior is left entirely to the `before` schema field and the return payload is deferred to an external URL rather than described.

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 lead sentence is well front-loaded, but the second and third sentences overlap ("recent activity" vs. "latest transactions") and the trailing "Outputs explained: GET /api/tools/history" is a cryptic endpoint reference of questionable value to an agent. Editing would tighten it without losing 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 4-parameter read tool with full schema coverage and no output schema, the description covers purpose, ordering, success/error reporting, and cost, which is enough to call it correctly. The one real gap is what the next-page cursor looks like on return, which is only hinted at in the schema.

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 every parameter including `before`, `network` and `how_many` is already documented in structured fields. The description only restates this via an example payload ({"wallet": "<address>", "how_many": 5}), which aids invocation but adds no semantics beyond the schema. Baseline 3 is appropriate.

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 concrete verb and resource: it "lists a wallet's latest transactions, newest first," and adds that it can also surface a real transaction ID. It implicitly steers the agent away from fabricating IDs for downstream tools, but it never names a specific sibling like check_tx or explain_tx to draw the boundary crisply.

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?

"Run to see a wallet's recent activity or get a real transaction ID. Never make one up" gives a clear triggering condition and an important prohibition on invented IDs. It does not spell out when to prefer this over check_tx, explain_tx, or tx_matches, so the exclusion is only implied.

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