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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: unknown hashes return 404 uncharged, failed calls are free, and repeats are billed because idempotentHint=false. The only reason this is not higher is that the pricing/key-mechanics detail crowds out return-shape nuance, but on balance it does add real behavioral value.

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?

Purpose and routing alternatives are front-loaded in the first two sentences, which is the right order. The pricing/credits sentence is longer than most agents need and could be trimmed, but it is not padding so much as commercial context.

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 single-parameter read tool with no output schema, the description fully covers input format, what the response contains, error behavior on unknown hashes, and cost model. Nothing an agent needs to call it correctly is missing.

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 100% and the single parameter already documents the 0x-prefixed 64-hex format, so the description's restatement adds little. The concrete example hash is a small practical aid, but the semantics are already carried by the schema.

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 first sentence names a specific verb ('look up') and resource ('a Berachain transaction by hash') and enumerates exactly what is returned: sender, recipient, value in BERA, nonce, gas limit, function selector, and block. It is trivially distinguishable from bera_receipt and bera_logs, which are named explicitly.

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 description gives explicit routing: use this to see what was sent or whether a tx exists; use bera_receipt for success/failure and fees; use bera_logs for emitted events. That is when-to-use plus two named alternatives with the selecting condition.

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