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

With no annotations, the description carries the full behavioral burden. It implies a read operation via 'get' and states prerequisites ('Requires: exchange, symbol'), but says nothing about freshness/caching, rate limits, auth, or what happens on an unknown symbol. Most of the text is a return-value catalogue rather than disclosure of behavioral traits.

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, but the body is one sprawling multi-clause sentence cataloguing every returned field, which is dense and hard to scan. Given there is no output schema the enumeration is not pure waste, but it is not economically structured either.

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 does the heavy lifting by enumerating the returned blocks (rating, coverage, bti, routes, warnings), which is genuinely necessary here. It stops short of describing error behavior or data freshness, but an agent has enough to invoke and interpret 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 description coverage is 100% and both parameters are documented in the schema with examples (BTC/USDT, binance/upbit/gateio). The description only restates 'Requires: exchange, symbol' with no added format, casing, or constraint detail, so 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 ('get') and resource ('token intelligence') and enumerates the exact contents: rating with 15-step grade_detail, per-venue grades, unanimous-club membership, microburst score, warnings, prediction hit-rate, KG fill, spread, transfer routes, coverage, and bti. An agent can tell this is a broad aggregator rather than a single-metric tool. However, it never names the closely-related siblings (get_token_research, get_microburst, get_unanimous, get_warnings) whose outputs it appears to bundle, so the boundary is left to inference.

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?

Gives an explicit imperative: 'Call this FIRST before deciding what to do with a token,' which is strong, actionable routing guidance. It does not, however, state when NOT to use it or how it relates to the granular sibling tools that surface the same signals, so an agent cannot tell whether a narrow call is ever preferable.

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