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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description usefully adds "bounded read-only RPC calls" and "deterministic" output framing, but says nothing about cost, rate limits, latency, or why idempotentHint is false despite a previous_state parameter for change detection.

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?

A single dense sentence, front-loaded with the verb and scope, with no filler. It is long but every clause carries information; a slight readability cost from packing the return fields into the same sentence.

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?

An output schema exists, so the description need not enumerate return values, and it still briefly signals what comes back (signals, evidence, coverage, follow-up). The main gap is routing: nothing tells the agent when to prefer this over transaction_intelligence or chain_contract_call.

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 the baseline is 3, but the description adds a constraint the schema does not encode: the three target parameters (address, contract_address, transaction_hash) are mutually exclusive and exactly one must be supplied. That is genuine meaning beyond the schema, which requires only chain.

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?

Specific verb (Inspect) plus tightly scoped resource (exactly one Base/Ethereum transaction, address, or contract), which maps cleanly onto the three mutually exclusive target parameters. It does not, however, name or differentiate itself from close siblings like transaction_intelligence or chain_contract_call, so an agent must still infer which tool to reach for.

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?

"Inspect exactly one ..." conveys a cardinality constraint (one target per call, no batching) but gives no explicit when-to-use vs when-not-to-use guidance and never mentions the sibling tools. Usage is implied rather than stated.

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