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

Annotations already declare this a safe, idempotent, read-only, open-world operation, so the safety profile is covered. The description adds only the conceptual definition of funding rates, nothing about freshness ('current' is vague), cross-exchange coverage limits, or rate limiting. With annotations doing the heavy lifting, a 3 is appropriate.

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?

A single efficient sentence with the resource front-loaded and no filler. It is appropriately sized, though it is arguably too thin for the parameter documentation that is missing.

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 simple read-only lookup with one optional parameter the description covers what the tool returns in broad terms ('current funding rates across exchanges'), but it leaves the symbol parameter entirely undocumented and gives no hint about coverage or update frequency. No output schema exists, so the description carries that burden and only partially discharges it.

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?

One parameter (symbol) with 0% schema description coverage, and the description never mentions it. It does not say whether symbol is required, what form it takes, or what happens if it is omitted — a real gap given the schema is silent.

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 ('get current funding rates across exchanges') and adds a plain-language gloss of what a funding rate is. It is clearly distinguishable from siblings like get_price or get_open_interest, though it never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites or alternatives among the many get_* siblings. The gloss 'who pays whom to hold a perp position' explains the concept but gives no signal about when an agent should call this instead of get_open_interest or get_price.

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