chainpeek: get the current gas price

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real operational context: latency (0.2-1s), cost (USD 0.001), a free tier limit (10 reads/IP/UTC day), and an untrusted-data warning about on-chain strings. That is well beyond what annotations provide.

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?

Front-loads purpose, then alternative routing, then returns, timing, pricing and safety. Every element is useful, though the listed return fields overlap with the existing output schema and slightly pad the text.

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 an output schema present, return-value details are optional, yet the definition still covers latency, pricing, rate limits, safety and a docs link. For a one-param read tool, nothing an agent needs to call it correctly is missing.

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 the single 'chain' parameter is a self-explanatory enum. The description restates the three valid chains, matching the enum but adding no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 a specific verb ('read') and resource ('the current gas price') plus the exact scope (Ethereum, Base, Robinhood Chain). It also distinguishes itself from the sibling estimate_gas, so an agent can separate the two without opening either schema.

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 routes the agent: 'For the gas units a transaction needs use estimate_gas,' which names the alternative and the condition under which it applies. The scope (current chain price) is clear, so when-not-to-use this tool is unambiguous.

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