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

The annotations already mark this as a read-only, idempotent, non-destructive operation, so the description's main contribution is the detailed list of what the inspection returns, including 'bounded ERC-20-shaped transfers' and 'recognized calldata' — useful nuance. No behaviors beyond the annotations are promised, and nothing contradicts the annotations.

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 entire description is one dense sentence that packs in all key details without redundancy. Every phrase adds value, and it is appropriately front-loaded with the core action.

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?

This is a simple single-parameter read-only tool with a rich output schema, so the description needs only to explain the tool's scope and key outputs, which it does thoroughly. The inclusion of USDC recognition and bounded transfers gives an agent enough context to decide when to call it.

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 schema already fully documents the single transaction_hash parameter with a clear description and example, achieving 100% coverage. The tool description adds no additional meaning about the parameter itself, so the baseline of 3 applies.

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 opens with a specific verb 'Inspect' targeting 'Base transaction status and receipt evidence', clearly differentiating from sibling tools like base-block-inspect or base-account-status. It enumerates concrete output facets (success/revert/pending, confirmations, gas fees, calldata, ERC-20 transfers, USDC recognition), making the tool's purpose unambiguous.

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 implies usage for anyone needing transaction-level details in a single call, but it never explicitly contrasts it with sibling tools or states when not to use it. Sibling names like crypto.base-block-inspect suggest alternative scopes, but no direct guidance is provided, leaving the agent to infer from the name.

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