Get live Base mainnet gas

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

Description states the tool makes a real USDC payment, contradicting the readOnlyHint annotation (true) which implies no state change. Even though the description is transparent, the contradiction with annotations is a serious flaw, warranting score 1.

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 sentences, front-loaded with key functionality and critical warning. No filler; every part 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?

Covers return contents, payment cost, prerequisites, and usage restrictions well. Lacks output schema but not critical. Would be 5 if not for annotation contradiction.

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 already provides clear description for the sole optional parameter (target_url). The main description adds no further parameter-specific detail, so baseline 3 applies given 100% schema coverage.

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?

Description clearly specifies the tool returns live Base mainnet gas data including base fee, priority fees, and ETH transfer estimate. The verb 'returns' plus resource details make purpose unambiguous, and no sibling tools exist to confuse.

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?

Explicitly warns against repeated calls and loops due to real USDC payment, and prerequisites (funded buyer wallet with USDC/ETH) are stated. This provides excellent when-to-use and when-not-to-use guidance.

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