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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds a genuinely new behavioral fact the annotations do not carry: the call costs $0.01 USDC, which an agent must know before invoking. It stops short of explaining how payment is settled or any 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?

A single front-loaded sentence with the subject, scope, and price packed in without waste. Nothing could be removed without losing information.

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 one-parameter read tool with an output schema and full annotation coverage, the description supplies what is needed: what is checked, which chains, and the cost. The only gap is the absence of any steer toward or away from sibling oracle tools.

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?

With one parameter at 100% schema coverage, the schema already documents the accepted 0x EVM or base58 Solana format. The description's 'target EVM or Solana address' restates that rather than adding new meaning, so the baseline of 3 applies.

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?

Names a specific verb (audits) and resource (EVM or Solana wallet address) and enumerates the three data sources consulted (law enforcement blacklists, historical transactions, sanction risk scores). An agent can tell this is a reputation/sanctions screening tool, though it is not explicitly distinguished from the sibling solana_token_risk_oracle or address_normalizer.

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 — the check-before-interacting use case is inferable from 'audits' and 'sanction risk scores' but never stated. No when-to-use, when-not-to-use, or alternative tool routing is given, despite several siblings (solana_token_risk_oracle, address_normalizer, smart_contract_verifier) occupying adjacent space.

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