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

Annotations already declare this as a safe, idempotent read operation. The description adds useful non-obvious behavior: a block outside the best chain, including an unknown block, reports `in_best_chain: false` rather than failing. It does not discuss auth or rate limits, but those are less critical for this simple read.

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?

The description is short and front-loaded: the first sentence states the primary return semantics, and the following sentence clarifies the orphaned/unknown edge case. The docs link and REST provenance are compact and do not distract.

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 low-complexity one-parameter read tool with annotations and an output schema, the description covers the main behavior and edge case adequately. It omits explicit alternatives to sibling block tools and does not explain the hash parameter, but the schema and output schema cover much of the remaining burden.

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 single `hash` parameter is only indirectly referenced through the REST path placeholder `{hash}`. The schema itself supplies the 64-hex pattern, examples, and BlockHash definition, but the description adds no meaningful guidance on the required format or meaning. With the context signal showing low schema description coverage, the description should compensate but does not.

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 read operation and its key return semantics: best-chain membership, height, next block hash, and the `in_best_chain: false` case for orphaned/unknown blocks. It clearly distinguishes status from retrieving a full block, but does not explicitly contrast itself with siblings like `get_block` or `get_block_header`.

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 implied: check whether a known block hash is in the best chain and get its height/next hash. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives among the many block-related sibling tools.

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