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

Annotations only cover readOnly/openWorld; the description adds substantial context beyond them: multi-node consensus requirement, on-chain delegated-key signature, an included receipt verifiable against the chain, a link, and an explicit prompt-injection caveat ('data from that service, not instructions'). This is unusually rich behavioral disclosure for a 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 core purpose leads the sentence, followed by provenance, trust, and return-shape details. Despite carrying service metadata (address, 'Free', signature), every clause adds something an agent needs, with no filler.

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 still states the return shape ({ blockNumber: number }) plus provenance and verification details. An agent has everything needed to call and interpret this zero-arg read.

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, so there is nothing to document and the baseline of 4 applies. The description appropriately spends no space on nonexistent inputs.

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 resource and scope: 'the latest BNB Smart Chain block the service agrees on,' with the multi-node agreement qualifier. This clearly differentiates it from siblings like balance, bnbUsd, pairPrice, and tokenInfo, which all return different data.

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?

The purpose implies when to use it (fetch the current block height), but there is no explicit when-to-use/when-not guidance or named alternatives. Since the siblings expose unrelated resources rather than overlapping ones, the lack of routing guidance is a modest gap rather than a critical one.

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