get_v1_btc_derivatives_fee_curve

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

With no annotations, the description adequately discloses the data provided: fee curve targets and trend classification based on a 2h moving average, plus price and category. It is transparent about what the tool returns, though it does not outline rate limits or authentication needs.

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, efficient sentence that conveys all necessary information without waste. It is front-loaded with the core purpose and adds relevant details concisely.

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 zero-parameter tool with no output schema, the description sufficiently explains the return values. It covers the fee curve targets, trend classification, and metadata (price, category). However, it does not specify the exact structure or units, which might be needed for full clarity.

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?

The input schema is empty (0 parameters), so baseline is 4. The description adds meaning by explaining the output, but no parameter details are needed.

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 returns a Bitcoin smart-fee curve for multiple confirmation targets (1/3/6/12/24/144 blocks) along with trend classification, which is specific and distinguishes it from sibling tools like get_v1_btc_derivatives_mempool_pressure.

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 explicit when-to-use or when-not-to-use guidance is given. The description implies usage for obtaining Bitcoin fee curve data, but does not mention alternatives or context compared to other BTC derivatives tools.

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