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

No annotations are provided, so the description carries full burden. It discloses that it returns a verdict with a signed, offline-verifiable receipt, costs $0.05 per call via x402/USDC, and fuses three analyses. It does not elaborate on error handling or rate limits, but the core behavior is transparent.

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 somewhat repetitive: the first and last paragraphs essentially restate the same information. It could be more concise by removing duplication while preserving the key details about pricing and receipt.

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?

Given the complexity of fusing three separate functions and no output schema, the description adequately explains the tool's purpose, supported chains, input parameters, and pricing. It mentions a signed receipt but doesn't detail the verdict format, which is a minor gap. Overall, it is complete enough for an AI agent to decide when and how to invoke it.

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 has 3 parameters with 100% description coverage. The description adds meaning beyond the schema: clarifies that chain defaults to 'base', token can be EVM contract or SPL mint, and wallet is optional for counterparty screening. It also summarizes inputs as 'token (+chain, optional wallet)'.

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 clearly states it provides a GO/CAUTION/NO-GO pre-trade verdict fusing token safety, wallet screening, and market signal. It directly answers 'Should I buy this token now?' and distinguishes from sibling tools like crypto_token_safety, compliance_wallet_screen, and crypto_signal_fusion by positioning itself as a replacement for three separate calls.

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 description explicitly says 'Should I buy this token now?' and explains it replaces three separate calls, giving clear context for when to use it. It also states supported chains (EVM + Solana) and pricing. However, it does not explicitly specify when NOT to use it, though the purpose is well-defined.

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