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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered; the description adds useful semantic context about what Mimir values actually are. It does not disclose scope (global protocol vs node-scoped), whether the full key set or a filtered subset is returned, or how it relates to the node/admin variants.

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 tight sentences, front-loaded with the return value and followed by an explanation of the values' role. No filler, though the second sentence could have been spent on sibling differentiation instead of defining Mimir.

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?

For a zero-parameter read tool with no output schema, the description adequately covers what is returned, but it leaves the most consequential open question unanswered: how this differs from get_mimir_node, get_mimir_admin, and get_mimir_key. That ambiguity is material given how many near-identical Mimir siblings exist.

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 and the schema is trivially complete at 100% coverage, so the baseline of 4 applies. The description correctly implies no inputs are needed to fetch the configuration set.

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 protocol configuration parameters / Mimir values), and even explains what the values are semantically (key-value pairs controlling fees, limits, feature flags). However, it gives no signal distinguishing it from the closely-named siblings get_mimir_admin, get_mimir_key, and get_mimir_node, which an agent must disambiguate before choosing.

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 offers no when-to-use guidance, no exclusions, and never mentions the alternatives (get_mimir_admin, get_mimir_node, get_mimir_key) that return overlapping Mimir data. An agent has to infer that this is the global/default view from the name alone.

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