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

With no annotations, the description carries the full burden and does reasonably well: it discloses that output is JSON, that the call is a read-only capability assessment with no side effects, and that there is a cost ('$0.003 USDC via x402'), which is meaningful payment context an agent needs before calling. It does not state latency, rate limits, or what happens on an unverified/non-proxy contract, so it falls short of fully transparent.

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 front-loaded and segmented into use-case, input, output, and example, with no filler sentences. The trailing pricing line sits awkwardly at the end and the bare '?address=...' example is more cryptic than illustrative, which are the only real blemishes.

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, so the description must enumerate return values, and it does so thoroughly: capabilities, matched functions, proxy implementation, role holders, paused state, and holder frozen status/balance. For a moderately complex multi-chain read tool this is nearly complete; interpretation guidance and edge-case behavior (non-proxy contracts, unverified source) are the remaining gaps.

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 all three parameters are already documented in the schema and baseline is 3. The description does restate useful defaults ('chain: ethereum default, base') and clarifies that holder additionally returns blacklist/frozen status and balance, but it adds little syntax or format detail beyond the schema itself.

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 names a specific verb-and-resource: determine what an issuer can do to holders of an ERC-20 on Ethereum or Base, enumerating capabilities like mint, pause, freeze, and seize. This is clearly distinct from sibling tools such as base_token_risk or token_report, though it never explicitly names a sibling to contrast against, which keeps it short of a 5.

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?

'Use when an agent must know what an issuer can do to holders' gives a concrete triggering condition and scopes it to stablecoin/RWA/ERC-3643 tokens on two chains. There is no exclusion guidance — nothing says when to prefer stablecoin_freezes or base_token_risk instead — so the agent must infer boundaries from the surrounding tool list.

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