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

No annotations are supplied, so the description carries the full disclosure burden; it does add real behavioral value by enumerating the response contents and disclosing the $0.02 cost up front. It stops short of stating read-only vs mutating nature, permission/auth requirements, or rate limits, which keeps it out of the top band.

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?

One dense sentence with the price front-loaded, then the input modes, then the output payload. Every clause carries information, though the parenthetical enumerations of aliases and tier names make it heavier than a purely scannable definition.

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?

Inputs and return contents are well covered and no output schema exists to offload them, so the coverage is broadly adequate. It is silent on which parameter combination is mandatory in practice (required=0 in the schema) and on how it differs from the overlapping token_profile sibling, leaving a real gap for correct invocation.

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 75% (chain, token, address, currency all carry descriptions or an enum), so baseline is 3. The description goes further by explaining how the parameters combine per input mode (address+chain vs token alias vs chain=xrp with issuer and currency), which the schema does not express.

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 states a specific deliverable (a 'token verdict card') over clearly enumerated resource domains: ERC-20 on Base/Ethereum, registered aliases, and XRPL issued currencies. It also lists the exact outputs (0-100 score, verdict tier set, transfers, wallets, mints/burns, concentration, whale flags). It does not, however, differentiate itself from the sibling token_profile, which an agent would likely confuse it with.

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?

Usage is only implied through the three accepted input forms (address+chain, token=alias, chain=xrp+issuer+currency). There is no explicit when-to-use, when-not-to-use, or named alternative among diligence_memo/token_profile/wallet_screen, so routing between siblings 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.