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

Annotations cover readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond them: the result is quorum-signed by an on-chain delegated key, carries a verifiable receipt, and is data rather than instructions (a prompt-injection guard). It does not cover rate limits or failure modes, but the safety and provenance picture is strong.

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 is front-loaded, but the sentence is cluttered with a full contract address, the '-- TapeAPI method' boilerplate, and repeated clauses. The prompt-injection disclaimer earns its place; the service-address verbosity does not.

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 compensates by enumerating the return shape { address, wei, bnb, blockPinned }, which is exactly what an agent needs. The block parameter and its default are covered. Only the sibling-differentiation gap keeps it short of full completeness.

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 description coverage is 100%, so baseline is 3. The description echoes the block-pinning concept and the address target but adds no syntax or default detail beyond the schema's '(default finalized)' note.

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 opening clause gives a specific verb+resource+scope: 'Native BNB balance of an address, pinned to one block.' The word 'Native' implicitly separates it from the sibling tokenBalance (ERC20 balances), though that distinction is not made explicit. Purpose is clear despite the surrounding boilerplate about quorum, service identity, and receipts.

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 states the tool is 'Free' and pinned to a block, which hints at usage, but never says when to pick this over tokenBalance or the other balance-adjacent siblings. An agent must infer the native-vs-token distinction from the word 'Native' alone.

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