estimate_smart_fee

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

With no annotations provided, the description carries the full burden. It discloses the valid range for confirmation target (1-1008 blocks), but lacks other behavioral details such as what algorithm 'smart' estimation uses, whether results are cached, rate limits, or output format details (though output schema exists).

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?

Extremely concise with zero waste. The two-part structure (purpose statement followed by Args documentation) efficiently delivers necessary information in minimal space. Every sentence earns its place.

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?

Adequate for a single-parameter tool with existing output schema. The description covers the parameter well and states basic purpose, but gaps remain in sibling differentiation and behavioral disclosure given the lack of annotations.

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?

Excellent compensation for 0% schema description coverage. The Args section clearly defines 'conf_target' as 'Number of blocks for confirmation' and provides the valid range (1-1008), adding critical semantic meaning absent from the schema's bare 'Conf Target' title.

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 core action ('Get fee estimate') and target ('specific confirmation target'), but fails to distinguish from four sibling fee tools (get_fee_estimates, estimate_transaction_cost, get_fee_recommendation, compare_fee_estimates). It does not explain what makes this estimation 'smart' or when to prefer it over alternatives.

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?

No guidance provided on when to use this tool versus the four alternative fee estimation tools available. No prerequisites, error conditions, or usage constraints are mentioned beyond the implicit parameter range.

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