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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds value by enumerating the returned position fields, which matters because there is no output schema, but it says nothing about behavior for an unknown/invalid address or about mutation of the underlying RUNEPool state.

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?

A single front-loaded sentence stating the resource and its returned fields, with zero filler. Nothing could be removed without losing information.

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 does the right thing by summarizing the return shape (deposited RUNE, units, PnL). It is nearly complete for a single-address getter, though it omits error behavior for unknown addresses and the denomination of the PnL figure.

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 description coverage is 100% (the address param is documented as a thor1... THORChain address), so the schema carries the parameter semantics. The description adds no format or validation detail beyond it, making the baseline 3 appropriate.

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 names a specific verb and resource ('Returns one RUNEPool provider's position') and enumerates the returned fields (deposited RUNE, units, PnL). The word 'one' implicitly contrasts with the list_rune_providers sibling, but it never names that sibling or disambiguates against get_runepool_member.

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?

There is no explicit when-to-use statement, no prerequisites, and no routing guidance. The sibling set contains both get_runepool_member and list_rune_providers, and the description gives the agent nothing to choose between them.

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