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

Annotations already declare readOnlyHint=true, so the safe-read nature is known without the description. The description usefully enumerates what data is bundled (bond metrics, pool data, node counts), but it does not address the odd idempotentHint=false for a parameterless read, nor return format or freshness/staleness of the data.

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 tight sentence that front-loads the verb and resource and then lists the payload categories. Nothing is wasted, though the phrase 'network statistics and health information' is slightly broad relative to the specific items that follow.

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 parameters and no output schema, the description must carry the full burden of what an agent gets back, and it partially does by naming data categories. However, it gives no way to distinguish this aggregate from the several sibling aggregate/stats tools, leaving a real selection gap.

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 clarify; the baseline for a 0-param schema is 4.

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 (THORChain network statistics and health information) with concrete content categories: bond metrics, pool data, node counts. It is clear on its own, but it does not differentiate itself from close siblings like get_network_summary, get_midgard_stats, or get_bonds, which appear to cover overlapping ground.

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 guidance on when to use this tool versus the many overlapping siblings (get_network_summary, get_midgard_stats, get_bonds, list_nodes). The agent is left to infer selection from the description alone, with no exclusions or alternative routing.

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