get_eth_gas_timing

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only adds 'Paid' (a cost indicator) and hints at the output (savings in gwei/ETH). It does not disclose whether the operation is read-only, what the response structure looks like, or any limitations such as rate limits or data freshness. This is a significant gap for a tool with no annotation support.

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 that front-loads the main value proposition ('Best time to send') and includes only essential details: the comparison (now vs. wait), the savings calculation, and the paid nature. No filler or repetition.

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's simplicity (2 optional params, no output schema, no annotations), the description covers the core purpose and hints at return values (savings), but it does not describe the response format or any additional behavioral details. It is adequate but not complete; the 'Paid' indicator is useful, but the description could mention what the output looks like or any prerequisites.

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% (both 'blocks' and 'gas_limit' have descriptions), so the schema already documents parameters. The description adds context that gas_limit is for calculating total savings, which aligns with the schema, but does not significantly extend beyond it. 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's purpose: determining the best time to send an Ethereum transaction, comparing sending now vs. waiting, and calculating savings. This distinguishes it from sibling tools like get_eth_gas_forecast, which focus on gas price predictions, while this one focuses on timing decisions. The verb is implicit but the outcome is specific.

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 the use case (deciding when to send a transaction) and mentions it is paid, but does not provide explicit guidance on when to use this tool versus alternatives like get_eth_gas_forecast or get_current_fees. There are no exclusions or alternative recommendations, so it falls at 'implied usage' rather than clear context.

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