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 covered. The description adds that results are ranked by volume/fees/TVL/fee-TVL, which is useful context, but it does not disclose default sort order, pagination, or 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 compact fragment with no filler, and the ranking metrics are front-loaded. It is terse enough that it reads more like a label than a sentence, but nothing is wasted.

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, no output schema, and annotations covering the safety profile, the essentials for invocation are present. However, the description never states the default sort or whether the ranking is applied server-side, which matters for a tool whose entire purpose is ranked output.

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%, with chain (enum plus pointer to chord_chains) and limit (default 25, 1-100) both documented. The description adds nothing beyond the schema, 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?

The description names the resource (pools) and the audience/ranking basis (for a liquidity provider, ranked by volume, fees, TVL, fee/TVL), which lets an agent distinguish it from chord_lp_positions and chord_tokens. It lacks an explicit verb like 'list' or 'rank', but the intent is unambiguous.

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 mention of the sibling chord_lp_positions (which an LP might confuse it with), and no statement of prerequisites or ordering. The audience hint ('for a liquidity provider') only weakly implies usage.

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