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

With no annotations, the description carries the full behavioral burden. It usefully discloses the $0.02 x402 cost, score range, confidence levels, and null behavior for stablecoins, but it does not explain payment/auth mechanics, error behavior, exact return shape, or rate limits.

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 a single compact, front-loaded sentence that packs the metric definition, range, confidence levels, stablecoin exception, usage context, and cost without filler.

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?

For a simple one-parameter metric endpoint with no output schema, the description gives enough to understand what is returned at a high level: score, confidence, and stablecoin nulls. It still leaves exact response format and edge-case/error behavior unstated, but the schema covers the optional-address and payment fallback details.

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 single optional address parameter is already well documented, including the x402 payment and preview fallback behavior. The tool description adds no parameter-level meaning beyond the schema, which is acceptable at the 3 baseline.

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 metric, chain, input signals, score range, and confidence levels, so it is clear what the tool computes. It also implies differentiation from the risk/holder siblings by framing the tool as a way to rank Base tokens by activity, but it does not explicitly name or contrast those alternatives.

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 guidance is 'Use to rank Base tokens by activity,' which gives a clear implied context but no explicit when-not-to-use conditions or named alternatives among holder_check, rug_check, token_risk, or token_verdict.

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