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

Annotations already establish that this is a read-only, closed-world call, so the description's job is to add operational context and it does: cost of $0.004 USDC, no charge on failure, auto-detection of token vs wallet, chain coverage, and the composite signal set behind the verdict. It stops short of describing latency, rate limits, or the exact response shape beyond verdict/score/reasons, which is why it is not a 5.

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 text is dense but front-loaded: cost and use case lead, then the return contract, then the signal set and chains. Every clause carries information; the only mild redundancy is that the $0.004 figure appears in both the title and the first token of the description.

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, the description carries the burden of explaining returns and it does so explicitly: verdict enum, numeric score range, and reasons. Combined with the stated pricing and failure policy, an agent has enough to call this correctly; only chain-default behavior and response size are left unspecified.

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 67%, and the description fills several gaps: it clarifies that the single address parameter accepts either a wallet or a token (auto-detected), lists the three supported chains, and explains the payment path implied by api_key including the no-charge-on-failure behavior. The one remaining ambiguity is what happens when the optional chain field is omitted, which neither the schema nor the description resolves.

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 pair: submit one address and receive a safe/caution/block verdict, a 0-100 score and reasons. It also enumerates the underlying checks (contract, holders, wallet profile, whale history, spam filters) and the supported chains, so the agent knows exactly what class of answer it gets. It does not explicitly contrast itself with close siblings such as token_verdict or lookup_token_risk, 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?

"Before paying or trading" gives a clear triggering context for when to reach for this tool. There are no explicit exclusions or named alternatives, so the agent must infer that this is the combined pre-transaction screening tool rather than a single-purpose lookup.

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