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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), but the description adds critical operational context the annotations cannot: $0.03 per call via x402 on Base, a prepaid x-credit-token header for unlimited calls, no free tier, and no API key required. It stops short of disclosing result limits or pagination.

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?

Front-loaded with purpose, and the em-dash style packs chain, returned fields, provider, and pricing into a compact block. Slightly run-on, but every clause carries 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?

With an output schema present, return-value explanation is not required, and the description still lists the fields. Pricing and auth are covered; the only real gap is how many transactions are returned and over what window.

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 coverage is 100% for the single 'address' parameter, so the schema already documents it; 'Required input: address' is largely redundant. The description does add that the address is a Base address, which is mildly useful framing.

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 resource (latest transactions for an address), names the chain (Base), and enumerates exactly what is returned (hash, time, from/to, ETH value, success). This distinguishes it from the many sibling wallet tools and from near_wallet_activity, which covers a different chain.

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?

'For agents tracking what a wallet is doing' implies a use case but gives no explicit when-to-use vs alternatives such as wallet_summary, wallet_portfolio, or near_wallet_activity. The agent must infer routing from the chain/recency scope alone.

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