getHistoricalInterestRate

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

With no annotations, the description discloses key behavioral traits: authenticated endpoint, permission requirement, data retention, parameter constraints, and URL encoding for 'No VIP'. Does not describe return format or rate limits, which are minor gaps.

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-loaded with purpose, then provides necessary details. Some redundancy exists between the main text and agent hint, but overall efficient.

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?

Covers auth, parameters, defaults, and constraints. Missing description of return format (since no output schema), but still provides sufficient context for a query tool.

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 has 0% coverage; the description fully compensates by detailing each parameter: currency required, startTime/endTime usage and constraints, vipLevel optional with default behavior, and encoding note. Adds substantial meaning.

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 'Query historical borrowing interest rate data for UTA spot margin.' This is a specific verb-resource combination that distinguishes the tool from siblings like getFundingRateHistory or getHistoricalVolatility.

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?

Explicitly outlines when to use: requires Spot permission, startTime and endTime together, max 30-day window, defaults to last 7 days if omitted, data available up to 6 months. Lacks explicit 'when not to use' or alternatives but provides strong contextual guidance.

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