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

The description discloses the most important non-schema behavior: the call costs 0.002500 USDC on Base mainnet, which also explains why readOnlyHint is false despite the 'Read' framing. It further instructs that the private idempotencyKey must be preserved for retries, aligning with idempotentHint=true. It stops short of describing rate limits or exactly which chain endpoint is hit.

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?

Three short, front-loaded sentences with no filler: identity/cost first, then the retry caveat. The machine-readable CAIP identifiers are dense but pay for themselves by naming the exact chain and payment network.

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 should say what comes back (the hash of the current best block) but does not. Cost and idempotency coverage is adequate for a zero-argument paid call, so the missing return-value meaning is the main gap.

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 50%; the idempotencyKey is already fully documented in the schema (private, persist before payment, reuse only for retries), so the description's retry note largely restates it. The unexplained 'params' parameter is an empty maxItems-0 array, which the description never clarifies must be empty.

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 verb ('Read') and a resource ('getbestblockhash') plus the chain identifier, but 'getbestblockhash' is essentially the tool name restated, so the agent gets little semantic meaning (that it returns the tip block's hash). It does not differentiate from the nearby sibling bitcoin_getblockhash, which is a plausible confusion point.

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 statement of when to use this tool versus the many sibling block/hash lookups. The only conditional guidance is about retry behavior with the idempotencyKey, which is operational rather than a selection criterion.

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