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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the non-idempotent hint is consistent with height=0 returning the latest block. The description adds the payload composition, but does not disclose anything about the 'canonical blockchain data' claim vs. siblings or about response size/pagination for blocks with many transactions.

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 short sentences, no redundancy, with the core return contract front-loaded. The trailing sentence ('Provides canonical blockchain data') is mild filler that doesn't carry actionable information.

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 does the minimum by naming the returned fields (header, transactions, commit signatures) and the caller can infer the height semantics from the schema. It is incomplete on the key differentiator for this tool set: how this differs from get_cometbft_block_results, get_cosmos_block, and get_block.

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 coverage is 100% and the height parameter, including the 'omitted or 0 returns latest' default, is fully documented in the schema. The description repeats the height scoping but adds no format, range, or error semantics beyond it, so 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 block data at the specified height') and enumerates the payload contents (header, transactions, commit signatures). It fails to distinguish itself from close siblings such as get_cometbft_block_results, get_cosmos_block, or get_block, which is a real ambiguity in this tool set.

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 when-to-use guidance and no mention of alternatives, despite the presence of several near-identical block retrieval siblings. The only routing hint is the parameter's own default behavior, which the schema already states.

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