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

Discloses source (redundant public RPCs) and pricing ($0.002/call), but does not mention read-only nature, error handling, caching, or rate limits. Since annotations are absent, this is a partial disclosure.

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 compact sentence packs the resource, output fields, source, and cost. It is front-loaded with the primary purpose and avoids fluff.

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 zero-parameter tool, it fully specifies the output (gas price, base fee, block number, timestamp), the source, and cost. No output schema exists, so this description serves as the agent's complete reference.

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?

No parameters exist, so the description adds nothing beyond the empty schema. Baseline 4 applies because the tool requires no input parameters.

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 exactly what it returns: current Base gas price, EIP-1559 base fee in wei and gwei, plus block number and timestamp. This clearly distinguishes it from sibling tools like base_block_number by focusing on gas price and fees.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention when to avoid it or which sibling covers other use cases, such as block number only. The cost note is informational but not a usage criterion.

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