explorer_get_daily_gas_used

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

Annotations already declare the tool read-only, so the description adds no extra behavioral context. The phrase 'daily average gas used' is ambiguous about whether the result is a single averaged value or a per-day series. No return format or timezone behavior is disclosed, leaving the agent uncertain about output semantics.

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, well-structured sentence that immediately conveys the tool's purpose. No wasted words or redundant restatements of the tool name.

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 simple read-only metric tool, the description is minimally sufficient but lacks important context: there is no output schema, so the response shape is undocumented, and no usage alternatives are noted. The annotations provide safety, but the description does not clarify the exact data returned.

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 description coverage is 100%, so all four parameters are already documented with meaningful descriptions. The tool description adds no additional parameter semantics beyond what the schema provides.

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 uses a specific verb ('Get') and clearly identifies the resource ('daily average gas used') and scope ('for a date range'). This distinguishes it from sibling explorer tools like explorer_get_daily_tx_count or explorer_get_daily_new_addresses.

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 when daily gas usage data is needed, but it does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions or prerequisites beyond the schema. No sibling differentiation is provided.

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