BinanceGetBorrowInterestRate

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 daily and yearly rates and supports multiple assets, which is useful. However, it does not mention response format, authentication, rate limits, or error behavior, leaving gaps in transparency for a read operation.

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 two sentences, front-loaded with the primary purpose, and contains no redundant or filler content. Every sentence adds relevant 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?

For a simple tool with two parameters and no output schema, the description covers the core purpose, return content (daily/yearly rates), and input format. It lacks a detailed response structure and omits the optional recvWindow parameter, but given the tool's simplicity, the description is reasonably complete.

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 100% for both parameters, so the baseline is 3. The description adds example assets (BUSD, BTC) but mostly reiterates the comma-separated list and asset limit already in the schema. It does not add significant new meaning beyond what the schema provides.

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 the tool retrieves borrowing interest rates, mentioning both daily and yearly rates for multiple assets. This distinguishes it from sibling tools, none of which cover borrow interest rate retrieval. The verb 'Retrieves' plus explicit resource makes the purpose unambiguous.

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 when you need borrowing interest rates and gives input formatting guidance (comma-separated list), but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. This is clear context but lacks explicit alternative guidance.

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