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

The annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds valuable operational context beyond that: Covalent as the data source, Base network, pricing, the optional prepaid header, and the lack of wallet/API key requirements. It also enumerates returned fields so an agent knows what to expect. No contradiction with annotations exists.

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 description is dense but well organized, front-loading purpose and output fields before pricing and authentication details. Every sentence adds operational or semantic value, with no filler or redundancy with the annotations.

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 one-parameter read-only tool that has an output schema and safety annotations, this description covers purpose, inputs, output fields, chain, cost, and authentication requirements. Nothing needed to invoke the tool correctly appears missing.

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?

The schema documents only 'address' as a wallet address, and the description adds that the address is a Base address and explicitly marks it as required. With 100% schema coverage, this is a modest but useful increment over the structured definition.

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 identifies a specific resource: recent transactions for a Base address, and names the output fields (hash, time, from/to, ETH value, success). This clearly distinguishes it from sibling wallet tools focused on balances, tokens, or net worth, and makes the read/list operation obvious.

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?

The phrase 'For agents tracking what a wallet is doing' gives a clear use case, and 'Required input: address' states the prerequisite. It does not explicitly contrast with sibling tools like wallet_tokens or wallet_portfolio, but the transaction-specific framing is enough to guide selection.

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