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

Goes well beyond the readOnlyHint annotation: discloses pricing ($0.01/call, first 25 free), that failed calls and rejected malformed addresses (400) are uncharged, that repeats are not free, and that the call changes nothing. These are exactly the facts an agent needs to avoid costly or pointless repeats.

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 the core behavior and alternatives before pricing details, and every sentence carries information. The single long opening sentence is dense and the pricing clause is somewhat crammed in, which keeps it from a 5.

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 compensates by describing the return shape (direction, counterparty, amount, transaction), the ordering (newest first) and the cap (up to 50). Nothing an agent needs to call or interpret the result is 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?

Schema coverage is already 100%, yet the description still adds meaning: the token parameter defaults to USDC, the block window is 1-2,000 with a 1,000 default, and it supplies a concrete address example. It stops short of explaining token-ticker fallback behavior 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 specific verb+resource (list a wallet's ERC-20 transfers), the network (Berachain), the direction scope (in and out), and the lookback window. An agent can distinguish it from bera_token_balance and bera_logs without opening the schema.

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 concrete use cases ('confirm a payment arrived or see what was sent') and names the alternative explicitly with its selecting condition ('for the current balance use bera_token_balance'). The boundary is unambiguous.

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