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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by enumerating return fields (units, pending amounts, deposit values, addresses), but it does not explain the idempotentHint=false declaration, pagination, or completeness guarantees for a list call.

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?

Three short sentences, front-loaded with the core behavior and the return shape. The closing 'Use this to analyze pool participation' is the weakest sentence but is not verbose enough to harm readability.

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 exists, and the description compensates by naming the fields each entry contains. The single required parameter is covered and the read-only nature is declared, leaving only minor gaps around result size/pagination and sibling routing.

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?

With one parameter at 100% schema coverage, the schema already documents 'asset' with an example format. The description's 'for a specific pool' merely echoes that, adding no format or constraint detail beyond the schema, so the baseline 3 applies.

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 and resource ('Returns all liquidity providers') and scopes it ('for a specific pool'), so the agent knows exactly what it retrieves. It does not explicitly differentiate itself from adjacent siblings like list_rune_providers or get_lp_position, so it stops short of a 5.

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?

'Use this to analyze pool participation' is a vague purpose statement rather than actionable guidance. There is no indication of when to prefer this over get_lp_position, list_rune_providers, or get_midgard_member, and no exclusions or prerequisites are given.

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