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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description still adds genuine value: it discloses that the two price-change series differ by the ADA/USD move, that flags are rule-based with per-flag evidence, and that pools and a safety assessment are included. What is missing is failure behavior for unknown units and data freshness, but the return-content disclosure is well beyond annotation coverage.

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?

It is one very long sentence, but it is front-loaded with the core purpose and each clause adds distinct information (the ADA/USD delta caveat and the per-flag evidence note are non-obvious). Slight deduction for a wall-of-text metric list that an agent must parse rather than scan.

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 carries the burden of describing returns and does so thoroughly, and annotations handle the safety profile. Completeness gaps are minor: no statement on unknown-token behavior, caching/freshness, or why one would choose this over the specialized token endpoints.

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 schema itself already documents the 56-hex policy-id + hex asset-name format and where to obtain it ('search' or 'list_tokens'). The description contributes nothing about the `unit` parameter, so the baseline 3 for a fully documented single parameter 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?

Opens with a specific verb+resource framing ('Everything about one Cardano token') and enumerates exactly which metrics are returned, so the agent knows this is the composite/aggregate view. That aggregate framing implicitly differentiates it from get_token_prices/get_token_safety/get_token_liquidity, but no sibling is named explicitly, 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?

The closing sentence gives a use case ('price, liquidity or risk questions about a specific token'), which is real but generic. It never says when to prefer the dedicated siblings (get_token_safety, get_token_prices, get_token_candles) over this heavier aggregate call, which is the main routing decision an agent faces here.

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