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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful output-shape context (which fields come back) and the caveat 'where it is known', which signals that wallet attribution can be missing — a genuine behavioral detail not present in the annotations.

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 front-loaded sentence with no filler; the field list is compact and immediately useful. The trailing clause 'and the wallet where it is known' is slightly awkwardly phrased but still information-dense rather than wasteful.

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 correctly compensates by listing the returned fields, which is the most important omission it could have covered. What remains unstated — ordering (only implied by 'newest'), default/pagination behavior, and real-time vs cached freshness — is minor for a simple read tool with fully described parameters.

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%, so chain, address and limit are already documented with enum values and format notes for EVM vs Solana addresses. The description only implies the address parameter via 'of a token' and adds no new format, ordering or default-limit semantics, 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 verb+resource — the newest swaps of a token — and enumerates the returned fields (side, USD size, price, venue, wallet). The 'of a token' scoping implicitly distinguishes it from the sibling chord_wallet_trades, but the description never names that sibling or otherwise explicitly differentiates itself from tools like chord_swap_tx.

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 guidance, no prerequisites, and no named alternatives. An agent must infer from 'newest swaps' that this is for recent token-level trade activity rather than aggregated candles (chord_candles) or a single transaction lookup (chord_swap_tx).

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