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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: data is live from chain, and the pool-pricing trap (raw balance ratios only yield spot price for constant-product pools). It loses a point for restating read-only/keyless twice rather than adding new behavior detail.

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?

The core purpose and the pricing caveat are front-loaded, which is good. But 'Free, keyless, read-only. Cost and signer: free and keyless, nothing to sign' says the same thing twice in two sentences, and that redundancy crowds out more useful detail.

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?

An output schema exists, so return values need no explanation, and with zero params the calling surface is trivial. The description covers what is returned, its live-from-chain freshness, and the main interpretation pitfall — enough for an agent to call and use it correctly.

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?

There are zero parameters, so the baseline is 4. The description's 'Every pool we provide liquidity to' correctly signals the tool takes no filters and returns an unscoped full listing.

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: every pool the entity provides liquidity to, with reserves and ownership share read live from chain. That is more concrete than the title. It doesn't explicitly contrast with crypto_tokens or crypto_wallets, but the noun 'pool' / 'liquidity positions' is distinctive enough that confusion is unlikely.

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?

No explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. The pool-pricing caveat implies usage guidance (don't derive spot price for concentrated-liquidity pools from these numbers), but that is interpretation guidance rather than tool-selection guidance.

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