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

With no annotations, the description carries the full burden and does well: it discloses that this is the LIVE predicted rate sampled over time (not settled payments), the row grain (one row per venue per time bucket), unit semantics (fraction per settlement interval), and the funding_hours interval values (1, 4, 8). It omits auth, rate limits, and pagination behavior, which keeps it short of a 5.

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?

Front-loads the output shape, then annualization guidance, then the routing rule to the alternative tool. Dense but every sentence serves a purpose; the run-on formatting is slightly harder to scan than a clean bulleted list.

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?

An output schema exists so return values needn't be restated, yet the description's column-level detail is genuinely additive for interpreting funding_rate. For a two-parameter read tool with no annotations, this is nearly complete; only operational details like limits or pagination are absent.

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 0%, so the description must compensate, and it does: it documents the symbol format ('BASEUSDT') and the range for minutes ('5 to 20160'). It never explicitly says minutes is the lookback window, but the time-bucket framing makes the intent inferable.

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?

States a specific verb+resource and the exact output shape: 'Funding rate over time for one contract, one row per venue per time bucket'. It also explicitly contrasts itself with the sibling get_funding_settlements, so an agent can distinguish the two without opening either schema.

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?

Names the alternative tool get_funding_settlements and the condition that selects it ('for the rates actually paid at each settlement'), and clarifies this tool returns the live predicted rate sampled over time. It gives clear context but does not mention other nearby siblings such as get_funding_rates or get_funding_dispersion, so no full exclusion set.

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