Get gas price

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

Explicitly labels as read-only and mentions the additional L1 data fee for Base, disclosing key behavioral traits. No annotations present, so description carries the full burden.

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 with no fluff, front-loaded with the core purpose, and efficiently adds a caveat without extra verbosity.

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?

With no output schema and only one parameter, the description could elaborate on return format (e.g., units) or error handling. The L1 fee note is helpful but the overall explanation feels minimal.

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?

Despite 0% schema description coverage, the description provides no information about the 'chain' parameter, its enum values, or default. Schema alone does not explain the purpose of each chain option.

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 the action (get) and resource (gas price) clearly, with elaboration on EIP-1559 fee suggestion. Differentiates from sibling tools about tokens and balances.

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?

Provides a specific use-case note about Base L1 fee, but does not explicitly contrast with other tools or state when to avoid using this tool.

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