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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: 'bounded' (gas limit), 'resolved Base mainnet block' (block resolution once), 'retain call and block evidence' (evidence retention), and the limitation that only primitive ABI types are decodable. This goes beyond structured data.

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?

One dense sentence that front-loads the core action ('Execute...') and packs in essential qualifiers ('bounded', 'read-only', 'resolved', 'retain evidence', 'optionally decode') without waste. Every clause earns its place.

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?

Given the rich schema (6 params, output schema) and clear annotations, the description provides enough high-level context: it explains the tool's scope (single call), block resolution, evidence retention, and optional decoding. It does not elaborate on error handling or response structure, but those are covered by the output schema and specifications.

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 each parameter has a detailed description (e.g., block_tag 'resolved once', gas_limit 'bounded', from_address 'no private key or transaction'). The main description does not add significant per-parameter meaning beyond these schema descriptions, so baseline 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 names a specific verb ('Execute') and resource ('read-only eth_call against a resolved Base mainnet block'), and clarifies scope with 'one bounded' and 'optionally decode caller-specified ABI output types'. This clearly distinguishes it from sibling tools like base-contract-inspect or base-event-logs.

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 (e.g., when a low-level contract read is needed) but does not explicitly state when to use this tool over alternatives or when not to use it. It provides no exclusion criteria or named sibling alternatives, so guidance is limited to what can be inferred from the stated purpose.

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