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

Goes well beyond the readOnly/openWorld annotations: malformed addresses return 400 uncharged, results are capped at 50 newest-first, repeats are billed, and pricing ($0.01/call, 25 free, failed calls free) is disclosed. The only shortfall is that it doesn't state how a partial/truncated history is signaled when the cap is hit.

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-loads purpose, then constraints, then the alternative, then pricing — a sensible order with no filler. It is dense, however: the billing clause is a long trailing run of conditions that could be tightened.

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?

There is no output schema, and the description compensates by enumerating the returned fields (direction, counterparty, amount, transaction), ordering, and the 50-row cap. Combined with the charge model, an agent has everything needed to call it and interpret the result.

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 the schema already documents token, blocks and address, including the ranges and defaults that the description restates. The one addition beyond the schema is a concrete example address, which is helpful but marginal, so the baseline applies.

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 and resource: list a wallet's recent transfers of one ERC-20 token on Scroll, both directions, including which fields come back and the ordering/limit. It is instantly distinguishable from the sibling scroll_token_balance, which it names.

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 explicit use cases ('confirm a payment arrived or see what was sent') and an explicit alternative for the adjacent need ('for the current balance use scroll_token_balance'). Nothing about when to pick this vs. the sibling is left to inference.

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