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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful context by naming the returned metrics, but it omits the notable behavioral fact that delisted/disabled strategies are excluded by default (includeDisabled), and says nothing about result volume or ordering.

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 short sentences, front-loaded with the resource and payload, followed by the filtering capability. No filler or redundant phrasing.

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?

With no output schema, the description usefully compensates by enumerating the fields returned. It falls short only on the includeDisabled default and any hint about result size, both relevant for a filterable list tool.

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 coverage is 75%, so the schema largely documents the parameters itself. The description maps three filters (chain, deposit asset, protocol) onto assets/chainIds/protocols, which adds little beyond the schema, and it completely omits includeDisabled, the one parameter whose default semantics are non-obvious.

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?

States a specific verb ('List') and resource ('Loopr leveraged strategies') and enumerates the fields returned (APY, leverage bounds, deposit/borrow tokens, TVL). It is clearly the plural/collection counterpart to the get_strategy sibling, though it never names that sibling explicitly.

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?

'Filter by chain, deposit asset or protocol' implies how to narrow results, but there is no explicit when-to-use guidance, no mention of when to call get_strategy instead, and no note that all filters are optional and the call returns everything by default.

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