evm_estimate_gas

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

There are no annotations to rely on, so the description carries the full burden of behavioral disclosure. It mentions 'real-time' and 'telemetry' but does not disclose whether this is a read-only operation, any rate limits, or what happens if the network is unsupported. The description is a bit vague about the exact behavior.

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?

The description is a single sentence with no fluff. It is concise and front-loaded with the main purpose ('real-time gas price and network execution telemetry'). No wasted words.

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 tool has only one parameter with full schema coverage and no output schema, the description is fairly complete. However, it could be more explicit about the output format or additional telemetry details, but for a simple query tool, it is reasonably sufficient.

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?

The schema description coverage is 100%, and the parameter 'chain' has an enum with descriptions for each value. Since the schema already explains the parameter, the description adds no extra meaning beyond what's in 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?

The description clearly states the tool provides real-time gas price and network execution telemetry across supported EVM networks. It distinguishes itself from siblings like evm_audit_contract, evm_fetch_source, and evm_decode_calldata by focusing on network-level telemetry rather than contract or transaction data.

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 for querying gas prices and telemetry, but it does not explicitly state when to use this over alternatives or provide exclusions. Given the sibling tools are quite different, the context is somewhat clear, but explicit guidance is missing.

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