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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond them: it discloses a per-call price ($0.003 USDC on Base via x402) and lists the returned fields in lieu of a missing output schema. It stops short of describing rate limits or error behavior, but the pricing disclosure is strong behavioral context.

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?

Two compact sentences, front-loaded with purpose and returned fields before the pricing note. Every clause earns its place with no redundancy.

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-argument read-only lookup with no output schema, the description adequately compensates by enumerating return fields and disclosing the x402 cost. The main omission is sibling differentiation against base_receipt/base_call when the agent is choosing between them.

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?

With 0% schema description coverage, the description says only 'by hash' — it does not explain that the hash is a 32-byte transaction hash or add format guidance. The schema's pattern (^0x[0-9a-fA-F]{64}$) does carry the format constraint, so the gap is partially covered, but the description itself adds little beyond naming the input.

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 verb+resource ('Base transaction details by hash') and enumerates the fields returned (from, to, value, calldata selector, block, status), so the agent knows exactly what this retrieves. However, it does not differentiate itself from sibling base_receipt or base_call, which are close in scope and could confuse selection.

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 explicit when-to-use guidance, no mention of alternatives, and no prerequisites stated. The agent must infer it should use this for transaction lookups versus base_receipt, base_call, or base_transfers purely from the name and field list.

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