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

No annotations exist, so the description fully carries the burden. It discloses DB-backed storage, 5-minute cache, 365-day retention with permanent monthly archive, and a 90-day max range, ensuring transparency about data freshness and limits.

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 front-loaded with the core action and quickly lists supported chains. It is slightly verbose with retention details but remains focused and readable.

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 7 chains, multiple fee types, and no output schema, the description thoroughly explains the data returned (e.g., 'ETH fast gwei, ETH standard gwei...'), caching, and retention. It is complete for agent decision-making.

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% for the single 'days' parameter, and the description adds minimal context beyond the schema (e.g., '1–90, default 30' matches the schema's default and range). No significant additional meaning is provided.

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 specifies the tool retrieves daily gas price history across 7 blockchain networks with exact units (gwei, lamports). It is distinct from siblings like 'gas' (likely current prices) and other analytics tools.

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 states it is 'useful for tracking gas fee trends and identifying high/low gas periods,' providing usage context. However, it does not explicitly state when to avoid using it or compare to alternatives like 'gas' for real-time data.

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