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 usefully adds the shape of the return payload (price, volume, trades, venues, index metadata), but says nothing about failure modes for invalid chain/address, or whether weather/index metadata can be partial.

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 tight sentence with the key scoping constraint front-loaded. 'What the index knows about it' is slightly vague filler but does signal extra metadata fields, so it mostly earns its place.

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 only two fully documented parameters and no output schema, the description's enumeration of returned fields (price, volume, trades, pools/venues, index info) is enough for an agent to decide to call it. Missing only the list-vs-detail routing relative to chord_tokens.

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%: both chain (with enum plus pointer to chord_chains) and address (EVM vs Solana base58, case-sensitive) are documented in the schema. The description adds no parameter-level detail beyond that, 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 resource and scope ('one token on one chain') and enumerates the payload: price, 24h volume and trades, pools or venues, and index metadata. However it never names the adjacent siblings (chord_tokens for listing, chord_candles for OHLC, chord_trades for trade history), so the agent must infer the boundary itself.

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 when-to-use or when-not-to-use guidance and no named alternative. The phrase 'one token on one chain' implies a single-entity lookup versus the plural chord_tokens, but that inference is left entirely to the reader.

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