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

Goes well beyond readOnlyHint/openWorldHint: discloses the four verdicts, that 'unknown is never reported as safe', 502-with-no-charge on total source failure, charging only on non-error results, invalid-argument rejection before settlement, and cache semantics (cached/stale/cacheAgeMs). This is exactly the failure-mode and cost information an agent needs before spending money.

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?

Front-loaded with the trigger and sources, which is good. But payment mechanics are stated three times (502/no-charge, 'charged only when the tool result is not an error', and the bracketed x402 pricing block), and the version string/metadata tail ('[falcon.sol solana-wallet-intel...]') duplicates earlier pricing content.

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 and 0% param coverage, the description supplies the return shape (verdicts, 0-100 score, flags with evidence, missing_fields) and the caching fields, which is substantial. Remaining gap is the undocumented 'network' param and no guidance on how verdict thresholds should change agent behavior.

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 0%, so the description must carry the load. It clarifies payTo (x402 payTo address) and endpoint (its unpaid 402 challenge, payTo mismatch, price outliers) and touches price indirectly, but never explains what the 'network' string should contain or how price is formatted/compared, leaving two of four params ambiguous.

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 and resource ('checks public sanctions lists... wallet age, activity and program status on Solana or Base') plus the endpoint's 402 challenge, and frames it as a pre-payment gate. Clearly distinct from siblings like token_check_demo, wallet_profile or pretrade, which do not combine sanctions + scam list + endpoint verification into a pay/no-pay verdict.

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?

Explicit trigger: 'Call this before your agent pays an unfamiliar x402 payTo address or endpoint', which also implies the when-not (already-known payees). It names the bundle companions (seller_report, pretrade) but does not say when to pick those instead of this one.

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