List Tegro Finance DEX pools

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

No annotations provided; description only states 'All liquidity pools' and a sentinel address. Lacks disclosure of rate limits, pagination, or data freshness. Mutation behavior not applicable, but still minimal transparency.

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?

Two sentences with no redundancy. First sentence clearly lists output contents; second sentence provides a sentinel address, which may be extraneous but not harmful.

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?

No output schema, so description must detail return values. Lists fields but does not specify structure (e.g., array vs object) or pagination. Adequate for a simple list but missing some context.

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?

No parameters in input schema (0 params), so schema coverage is 100% trivially. Description adds value by listing returned data fields, compensating for lack of output schema.

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?

Description clearly states it lists all liquidity pools and enumerates specific data fields (reserves, fees, LP supply, USD TVL, APYs). It is distinct from siblings like tegro_dex_pools_for_token but does not explicitly differentiate.

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 guidance on when to use this tool versus alternatives. Does not mention any prerequisites or intended use cases.

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