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

No annotations are provided, so the description carries the full behavioral burden. It discloses cost ($0.05), which is genuinely useful and beyond the schema, but says nothing about read-only nature, auth requirements, rate limits, or latency; for a mutation-free but possibly expensive forensics call this leaves major gaps.

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?

A single sentence that front-loads the cost and then the capability, with the output list tightly packed. No filler, though the comma-spliced enumeration is dense.

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, annotations, or high-coverage params, the description does list the returned dimensions — useful — but is silent on how to choose between token and address, what the $0.05 buys in terms of scope/limits, and how it differs from overlapping siblings. Adequate but under-specified for a 3-param paid forensics tool.

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 only 33%; the address pattern and token alias examples live in the schema, while the description merely repeats the chain enum ('Base or Ethereum'). It never clarifies the token-vs-address relationship (are they alternatives? both required?), so it fails to compensate for the coverage gap.

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 ('Full ERC-20 forensics profile') and constrains scope to Base or Ethereum, then enumerates the exact outputs (net supply change, mint/burn, holder concentration, transfers, whale moves). This distinguishes it reasonably from generic siblings like forensics_info, though it never names an alternative explicitly.

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 only usage signal is the price tag '$0.05', which implies a paid call. There is no statement of when to reach for this over token_verdict, forensics_info, or wallet_screen, nor any prerequisite (e.g., which of token/address to supply).

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