getLPPoolInfo

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

No annotations provided, so description carries full burden. It lists output contents but does not disclose potential side effects, performance, or data freshness. As a read-only query, basic transparency is present but could be improved.

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?

Four sentences with clear structure: purpose, usage context, agent hint, and parameter requirement. No unnecessary words; each sentence adds value.

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?

Given no output schema and only one parameter, the description covers purpose, usage, and parameter source. Lists included information (APY, fees, etc.) giving a sense of output, but lacks return structure details.

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 has 0% coverage, and description adds 'poolAddress is required and must come from getLPPoolList,' which specifies the source and necessity of the parameter, adding meaning beyond the schema's type declaration.

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 starts with 'Query detailed pool information including APY breakdown, fees, token reserves, and historical performance,' using a specific verb and resource. It clearly distinguishes from sibling getLPPoolList by indicating this provides details for a specific pool after selection.

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?

Explicit guidance: 'Use this after selecting a pool from the pool list' and 'Call this before staking to show the user complete pool details.' Also states poolAddress must come from getLPPoolList, providing clear context and prerequisite.

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