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

Annotations already establish readOnlyHint=true, so safety is covered by structured data. The description adds the return shape (a map of mimir keys to voted values), which is useful, but says nothing about why idempotentHint=false (votes change over time), whether non-voting nodes return an empty map, or how large the result can be.

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 with no filler, front-loaded with the core action and followed by the return shape. It could be trimmed slightly since the third sentence partly restates the first, but nothing is wasted.

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 single-parameter read-only lookup with no output schema, the description covers what is fetched, for whom, and in what shape. The main remaining gap is disambiguation from the sibling mimir-vote tools, which would make it fully self-sufficient.

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% and the single address parameter is fully documented in the schema, including the thor1... format. The description only restates that the address identifies the node, adding no syntax or format detail beyond the schema. 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?

The description gives a specific verb and resource ("Returns the mimir settings voted by a specific node") and scopes it to one node address, which separates it from get_mimir and get_mimir_key. It does not, however, distinguish itself from the very close sibling list_mimir_node_votes, which an agent could easily confuse it with.

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 see what protocol parameters a specific node operator is voting for" supplies a clear use case, but there is no when-not guidance and no named alternative, despite list_mimir_node_votes and get_mimir_key being near neighbors. Usage is implied rather than routed.

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