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

With no annotations, the description carries the full burden and does disclose two non-trivial behaviors: pay-per-call billing ($0.01 USDC) and the chain-to-endpoint routing. It omits auth requirements, return shape, and rate/error behavior for a multi-chain aggregator, so transparency is partial rather than rich.

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 value proposition, followed by the returned fields, routing, and price in dense but ordered fragments. No filler sentences; slightly telegraphic endpoint syntax is the only mild readability cost.

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 no annotations, the description compensates by enumerating the returned data fields and the cost model, which is the key information an agent needs before paying. Auth requirements and response format remain inferable but unstated, leaving a small gap.

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 100% and the enum for chain plus the token format are both documented in the schema, so this is the baseline 3. The description adds only the per-chain endpoint paths, which restates the chain enum rather than deepening parameter meaning.

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+resource ('Full token due-diligence') and enumerates the payload (price, liquidity, 24h volume, DEX pairs, supply, EVM contract metadata), so an agent knows exactly what it gets. It does not, however, distinguish itself from close siblings such as token, trust_check, risk_check, or solana_token_report, which likely overlap on the same asset.

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 phrase 'in ONE call' implies this is the aggregate/everything option and the stated $0.01 USDC pay-per-call is a real selection consideration. But there is no explicit when-to-use vs when-not, and no routing guidance against token/trust_check/solana_token_report, leaving the agent to infer the choice.

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