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

The annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered by structured data. The description adds one piece of context beyond that — that data comes from the gRPC-gateway REST API and is 'canonical' — but it does not explain the odd non-idempotent hint for a pure info fetch, nor any latency, caching, or failure behavior.

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 sentences, front-loaded with the core purpose; nothing is redundant or padded. The trailing sentence about the gRPC-gateway REST API is only marginally useful for tool selection, keeping it just short of a perfect score.

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 describing returns, and it does list the returned fields, which is adequate. But against a large sibling set with several near-duplicate node/network/version tools, it lacks the differentiation an agent needs to select correctly.

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 (schema coverage 100% by default), so per the rubric this is a baseline 4. There are no inputs whose semantics the description would need to clarify.

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 states a specific verb and resource ('Returns Cosmos SDK node information') and enumerates the returned fields (network, version, protocol versions, application version), so the purpose is unambiguous. However, it makes no attempt to distinguish itself from close siblings such as get_node, get_network_info, get_version, or get_cometbft_status, 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?

There is no guidance at all on when to call this tool versus the several sibling tools that return overlapping network/version/node data. No prerequisites, no exclusions, no alternatives are mentioned; the agent must infer usage entirely.

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