thorchain_get_pools

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

With no annotations, the description must carry the burden of behavioral disclosure. 'Get all available' suggests a read-only operation returning a list of pools, which is basic transparency. However, it does not discuss potential limitations (e.g., pagination, rate limits, response size) or what 'available' exactly includes, so it adds limited context beyond the tool's name.

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 description is a single, succinct sentence: 'Get all available THORChain liquidity pools.' Every word contributes to the meaning, with no redundant or irrelevant content. It is appropriately sized for a zero-parameter tool.

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 the tool's simplicity (zero parameters, no output schema), the description is nearly complete. It clearly states the function and scope. However, because there is no output schema, a brief note about the return format (e.g., 'returns a list of pool assets') would enhance completeness, but it is not critical for a list-type operation.

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?

The tool has zero parameters, and the schema is empty (100% coverage). Per the rubric, 0 params earns a baseline of 4. The description confirms that no parameters are required, so the agent can invoke it without needing any argument details.

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 clearly states a specific action ('Get all available') on a specific resource ('THORChain liquidity pools'), which differentiates it from sibling tools like thorchain_get_pool_info (which fetches a single pool) and thorchain_get_balance. The scope ('all available') provides a clear distinction.

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?

The description implies that this tool is for retrieving the complete list of THORChain liquidity pools, not a specific one. However, it does not explicitly mention when to use this tool over alternatives such as thorchain_get_pool_info or note any exclusions, leaving the guidance somewhat implied.

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