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

readOnlyHint=true already covers the safety profile, so the description only needs to add context beyond that. It implies a filtering behavior by emphasizing 'verified PoolKeys' and 'indexed' pools, which usefully suggests unverified pools are excluded, but it says nothing about result ordering, limits, empty-result behavior, or whether the token order actually matters.

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?

It is a single front-loaded sentence with no filler, but the long comma chain of return fields reads as a run-on inventory and could be tightened. The most decision-relevant information (token pair + indexed pools) does come first.

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?

For a 7-parameter discovery tool with an output schema, the definition is serviceable but spends most of its words describing return contents that the output schema already defines, while omitting the usage guidance and filter behavior an agent actually needs. It is adequate, not complete.

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?

With 86% schema description coverage, the schema already explains most parameters, and min_tvl_usd even documents its default. The description's mentions of 'pool type', 'extension', and 'Core generation' loosely map to pool_type, extension, and core_address but add no semantics, and it never addresses the token_a/token_b order tolerance.

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 opens with a specific verb and resource ('List indexed pools for a token pair') and enumerates distinguishing content such as verified PoolKeys, Core generation, and the Positions/Ve33Positions manager. That is enough for an agent to tell it apart from a plain pool lookup, though it never names the siblings it replaces or complements (e.g., get_pool, list_pool_keys, discover_uniswap_pools).

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 or when-not-to-use guidance and no named alternative. The only routing signal is the title's 'for an LP position', which implies this is a discovery step before prepare_lp_position_deposit, but the description itself never says so or states prerequisites such as whether a position must already exist.

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