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

With readOnlyHint/idempotentHint already declared, the description still adds substantial value: the full set of EVM checks (honeypot sim, mint/blacklist/pause/fee functions, LP burn, buy tax, flow), the Solana-specific checks, and the returned verdict enum (LOW_RISK/CAUTION/HIGH_RISK). It answers what gets analyzed and what comes back, which annotations alone do not.

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 use case ('Due diligence before buying any token') and dense with distinct, non-redundant facts. The EVM/Solana check lists are long but each item carries screening meaning, so it stays informative without much waste.

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 multi-chain analysis tool with no output schema, the description covers chains, address formats, the checks run per ecosystem, the verdict taxonomy, and the sibling alternative. Nothing essential to correctly invoking or interpreting it is missing.

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% and both parameters are already documented, including the chain enum and the address format. The description restates the chain list without adding syntax or format detail beyond the schema, so the baseline 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?

States a specific verb/resource (token risk due diligence) with concrete scope and enumerates the exact checks performed for EVM and Solana mints. It explicitly distinguishes itself from the sibling token.swap_quote, so an agent can route correctly without opening either schema.

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 closing sentence gives both a when-to-use ('Use before buying a token') and a named alternative for the adjacent need ('for the price you would get on chain use token.swap_quote'). This is explicit routing guidance rather than implied context.

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