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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description's added value is the response shape — it tells the agent that identity, mark price, liquidity and listings arrive under `token` and activity metrics under `stats` — but says nothing about behavior on an unknown address or about data freshness.

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?

A single dense sentence with the lookup key front-loaded and the return payload split cleanly into `token` and `stats`. It is clipped into a fragment rather than a full clause, but nothing is wasted and the ordering serves a reader scanning for what comes back.

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 return-value burden and does so credibly by enumerating the fields in each response section. For a two-parameter read tool that is close to sufficient; the only real omissions are not-found behavior and the meaning of vaguely named fields like 'listings' and 'mark price'.

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 entries already explain the chain slug and the 0x/base58 address formats in more detail than the description. The description only restates the pair as the lookup key, so baseline 3 is correct — it adds no syntax or constraint beyond the schema.

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?

The description states a specific resource and lookup key: a single token identified by chain and contract address, with the two response sections named. It is distinguishable from list-style siblings such as search_assets or list_traders, though it never explicitly contrasts itself with get_token_candles, which the word 'token' alone could be confused with.

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?

There is no explicit when-to-use guidance, no statement of prerequisites, and no routing to alternatives. The phrase 'by chain and contract address' implies you must already know the address, which hints that search_assets is the discovery path, but the agent must infer that rather than being told.

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