get_funding_rate

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

Without annotations, description covers return structure (per-venue rates, annualized rates, next funding timestamps) but omits behavioral details such as read-only nature, error handling, or rate limits.

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?

Two concise sentences efficiently convey purpose and venue list without redundant text, but could be more front-loaded with key verb and resource.

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?

Though no output schema, description adequately explains return fields given simplicity of the tool; could be improved by hinting at JSON structure or error cases.

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 100% with examples for base_currency; description does not add additional semantic meaning beyond the schema, so baseline 3 is appropriate.

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?

Description states 'Get current funding rate for a perpetual futures contract' with specific verb and resource, lists supported venues, and clearly differentiates from sibling tools like 'get_price' which focuses on spot prices.

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?

Description implies usage for funding rates and lists venues, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools for related data like spot prices.

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