spraay_free_gas

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context: data is cached for 15 seconds and sourced from Alchemy. This helps the agent understand staleness and trustworthiness, going 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?

Two sentences with no wasted words. Front-loaded with the core purpose and key details (chains, cache, cost, safety). Every sentence adds value, and structure is optimal for quick scanning.

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?

The description covers the tool's purpose, data source, cache duration, cost, safety, and parameter usage. With an output schema present, the agent has enough to invoke the tool correctly. A minor gap is the lack of documentation on what keys the params JSON supports, but given the tool's simplicity, this is acceptable.

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% with a single parameter 'params' described as JSON. The description reinforces that query parameters are passed as a JSON string, adding clarity. While the schema already covers it, the description's example and instruction add marginal value.

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 retrieves gas prices across 7 EVM chains via Alchemy with a 15-second cache. The verb 'gas prices' and resource '7 EVM chains' are specific, and the name 'spraay_free_gas' distinguishes it from siblings like 'spraay_oracle_gas' by highlighting it's free.

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 notes it's free and read-only, which implies it's suitable for cost-sensitive or safe queries. However, it does not explicitly state when to use this tool over alternatives like 'spraay_oracle_gas' or provide when-not-to-use guidance. The usage context is implied but not fully spelled out.

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