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

There are no annotations, so the description carries the transparency burden. It does disclose that the tool aggregates data from CoinGecko, DeFiLlama, Etherscan, and Polymarket and includes AI risk assessment, which adds useful context. However, it reveals nothing about read-only behavior, permissions, latency, failure modes, or response handling for a potentially complex multi-source operation.

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 compact and front-loaded with the core purpose, followed by a source list. It wastes no words, though the opening noun phrase 'Multi-source token intelligence' is somewhat generic and the long enumeration could be better structured.

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 complex aggregator with no output schema and no annotations, the description gives a useful high-level map of capabilities and sources but lacks important completion details such as expected output shape, module-to-source mapping, error behavior, or limitations. It is sufficient for basic tool selection, not for fully anticipating invocation results.

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 description coverage is 100%, so parameters (query, chain, include) are already documented. The description adds no additional parameter-level detail such as accepted query formats, chain behavior, or how the include modules map to output sections. Baseline 3 is appropriate because the schema carries the load.

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 resource (token intelligence) and enumerates concrete modules (market data, DeFi metrics, contract verification, prediction markets, holder analysis, price history, AI risk assessment) plus the aggregated sources. It is clear about the tool's broad scope, but it does not explicitly distinguish it from closely named siblings like token_intel or token_risk_metrics.

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?

No guidance is given on when to choose this tool over the many similar sibling tools. The description implies it is a general multi-source token research tool, but it never states when to use it versus token_intel, token_compare, token_risk_metrics, or solana_token_risk_scan.

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