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 by structured data. The description contributes genuine extra context by explaining that bond providers include Bond Yield configuration (bps share and payout_target), but says nothing about permissions, error cases, or whether idempotentHint=false matters here.

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 front-loaded sentences with no filler; the core purpose leads and the Bond Yield detail follows as a qualifier. Slightly dense in the second sentence but every clause earns its place.

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 tool with no output schema and no nested objects, the description covers both what it returns and a notable conditional case (Bond Yield when set) – including the payout_target terminology an agent cannot derive from the schema. Missing only the rare edge/permission context.

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?

With one parameter and 100% schema description coverage, the schema fully documents the address argument (including its thor1... format). The description adds no syntax or format detail beyond the schema, so the 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?

States a specific verb (returns) and resource (a specific validator node) and enumerates the returned fields (bond, status, version, performance metrics). It implicitly distinguishes itself from the list-oriented siblings like list_nodes and get_midgard_nodes via 'a specific node', but never names them, so differentiation is inferable rather than explicit.

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?

Usage is only implied: an agent can infer this is the lookup when it already has a node address, versus list_nodes for enumeration. No explicit when-to-use, prerequisites, or named alternatives are given, and with many node-related siblings (get_midgard_nodes, get_cosmos_validators, get_cometbft_validators) this is a real gap.

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