getLPPoolList

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

With no annotations, the description carries full burden but discloses no behavioral traits beyond its function (e.g., read-only status, authentication needs, pagination, rate limits). Only states what it returns without deeper behavior context.

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?

Concise with a clear front-loaded purpose and an agent hint. Minor redundancy in 'AI agent can use this...' sentence, but overall well-structured.

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?

Covers high-level purpose and some return fields, but lacks details on response structure, error handling, or prerequisites. The tag-schema mismatch reduces completeness. No output schema exists to compensate.

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?

Description mentions tokenSymbol filtering and implies it's optional, but incorrectly adds a 'tag' parameter not in schema. Does not explain acceptable values or format for tokenSymbol, so adds partial but misleading value.

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?

Clearly states the tool queries available liquidity pools with optional filtering and lists returned fields (addresses, tokens, APY, TVL). However, it mentions filtering by 'tag' which is not in the schema, causing confusion, and does not explicitly distinguish from sibling tools like getLPPoolInfo.

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?

Provides an agent hint specifying when to use (browsing/searching pools by token) and how to filter. Lacks explicit when-not-to-use instructions or alternatives such as getLPPoolInfo for detailed pool info.

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