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 that the tool returns 'bucketed' historical data constrained by the `minutes` range, which implies a read-only operation. However, it does not explain bucket granularity, pagination, or behavior for invalid inputs, leaving some behavioral uncertainty.

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 with no filler. It front-loads the core concept ('bucketed funding-rate history'), then adds the concrete symbol example and the time range constraint. Every word contributes useful information.

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 low complexity (two parameters, simple types) and the presence of an output schema, the description covers the essential use case and parameter semantics adequately. It does not explain return fields, but the output schema likely covers that. The only minor gap is lack of detail on 'bucketing' behavior, but overall it is sufficient for correct invocation.

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 0%, so the description must compensate. It does so by giving a concrete symbol example (BTCUSDT) and specifying the valid `minutes` range (5-20160), adding meaning the raw schema lacks. It does not fully specify formatting or constraints beyond the range, hence not a 5.

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 identifies the resource as 'Bucketed funding-rate history per exchange for a symbol' with a concrete example (BTCUSDT) and a time window. It distinguishes itself from sibling tools like get_funding_rates by emphasizing 'history' and 'per exchange', though it does not explicitly name an alternative.

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 usage by explaining what the tool returns (historical, bucketed funding rates over a specified recent period) but provides no explicit guidance on when to prefer this over get_funding_rates or other funding-related siblings, nor are any exclusions or alternative tools mentioned.

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