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 the 'verbose' nature and the latest-block default, but does not explain the non-idempotent behavior (likely because the latest block changes) or any response-size/rate considerations for a verbose payload.

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 compact sentences with the core purpose front-loaded and the default behavior following. Every sentence carries information; no filler or repetition.

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 carry the burden of describing return contents and does so reasonably (header, transactions, results, hash, chain ID, height, validator info). The main omission is sibling disambiguation against the other block tools.

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 a single parameter at 100% schema description coverage, the schema already documents the optional height and its latest-block default. The description restates that default but adds no format, range, or edge-case semantics beyond the schema, so the baseline of 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 and resource ('Returns verbose details of a THORChain block') and enumerates the contents (header info, transactions, block events, hash, chain ID, height, time, validator info). However, it never distinguishes itself from the many block-related siblings such as get_cometbft_block, get_cosmos_block, or get_lastblock, so an agent cannot tell which block tool to pick from the description alone.

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?

It gives one useful usage cue: 'If no height is specified, returns the latest block.' But there is no guidance on when to prefer this over get_cometbft_block, get_cosmos_block, or get_lastblock, and no exclusions or prerequisites. Usage is implied rather than stated.

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