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

Annotations already cover safety (readOnly, idempotent, openWorld), so this is graded on added context. The description goes beyond them by disclosing cost mechanics (0.030 USDC per call, included in subscriptions) and analytical depth ('up to two hops' for OFAC/hack linkage), which materially affects agent decisions on batching and budget.

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?

Two sentences, no filler, and the core deliverable is front-loaded before the cost caveat. Every clause carries information about either scope or price.

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 compensates by enumerating the verdict components (exchange status, age, activity, bot/human, PnL on launches, exchange funding, OFAC/hack links). It also discloses cost. Only the response packaging/shape is left unstated, which is minor for a single-address lookup.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents the address input including its regex pattern. The description adds no format or sourcing nuance beyond that, making 3 the appropriate 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?

States a concrete output (a verdict with reasons) for a specific resource (a Solana address) and enumerates the dimensions checked, so the agent knows exactly what capability this is. It does not, however, differentiate itself from near-neighbors like describe_address or score_performance, which the agent must distinguish on its own.

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 title 'Should I deal with this address' plus the risk-signal list implies the use case (vetting an address before transacting), and the pricing line gives a cost consideration. But there is no explicit when-to-use/when-not guidance and no mention of when describe_address or score_performance would be the better pick.

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