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

Annotations already declare readOnlyHint=true, so the safe-read profile is established without the description. The description adds useful behavioral context by listing the components of the returned state, but says nothing about freshness, snapshot timing, or why idempotentHint is false for what appears to be a static state read.

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 sentence, front-loaded with the verb and resource, followed by a compact enumeration of returned fields. No filler, no repetition of the tool name or annotations.

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 carries the burden of conveying what comes back, and it does so by naming the five state components. It stops short of clarifying the aggregate-vs-member scope relative to get_runepool_member, which is the one thing an agent could still get wrong.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made that could conflict with the empty 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?

States a specific verb ('Returns') and resource ('RUNEPool state') and enumerates the concrete data returned: protocol-owned liquidity, provider shares, reserve position, deposit limits, pending deposits/withdrawals. It is clear what the tool does, but it never distinguishes itself from close siblings such as get_runepool_member or list_rune_providers, so an agent must infer the boundary.

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 is purely descriptive of output; it gives no when-to-use guidance, no prerequisites, and does not name an alternative such as get_runepool_member for per-provider detail. Usage is only weakly implied by the name and the aggregate nature of the fields.

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