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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds real behavioral value by spelling out what the live check performs (an actual sell-back test with taxes, an ongoing price/liquidity watch, a launch grade). It still says nothing about latency, caching, rate limits, or what happens for an invalid/unknown token address.

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 core purpose, then the data inventory, then the trigger for use; no filler sentences. The middle clause is a dense comma-separated list, but it stays readable and earns its space.

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, the description does the necessary work of describing the returned data (risk level, sell test, launch grade, price/liquidity/volume/holders). Annotations cover the safety profile. The one missing piece is sibling disambiguation against check_tokens_risk.

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?

There is a single 'token' parameter with 100% schema description coverage and an explicit address regex, so the schema fully documents it. The description adds no additional meaning (e.g., chain constraints beyond Robinhood Chain, token-type limits), which is the correct baseline of 3 when schema coverage is complete.

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 ('live Risk Level for a token on Robinhood Chain') and enumerates what the risk assessment covers (sell test, taxes, price/liquidity watch, launch grade). However, it never distinguishes itself from the near-identical sibling check_tokens_risk, leaving the agent to infer which one to call.

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 'Use it before suggesting any buy' gives one clear usage context, but there is no when-not guidance and no mention of the obvious alternative check_tokens_risk (plural/batch) for multi-token checks. Usage is implied rather than routed.

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