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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds real context on top: the data is limited to Base and Robinhood Chain, only covers activity since 1 Oct 2026, is returned newest first, and — via 'any wallet's' — that arbitrary addresses may be queried rather than only the authenticated user. It does not mention pagination or result caps, which is the remaining gap for a list 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?

A single dense sentence that front-loads the scope (chains, date floor, ordering) before enumerating returned fields; no filler and nothing repeated from the schema.

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?

With no output schema, the description helpfully enumerates the returned fields (token, amount in base units, dollars paid/received, price, transaction), which an agent needs to interpret results. Missing only result-size/pagination behavior for what is likely a long list.

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?

There is one parameter with 100% schema description coverage ('0x... address'), so the schema carries the load and baseline is 3. The phrase 'any wallet's' slightly reinforces that owner is not restricted to the caller, but no format or validation detail is added beyond the schema.

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 resource (stock-token buys, sells and transfers for a wallet) with explicit scope: two named chains, a start date, and newest-first ordering. The 'history' framing makes it distinguishable from wallet_holdings and wallet_pnl without opening their schemas, though it never names those siblings to sharpen the contrast.

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 only implied by the noun 'history' — an agent can infer this is the lookup for past transactions rather than current balances or P&L, but the description gives no explicit when-to-use statement and no exclusions or prerequisites.

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