BinanceGetLoanableAssetsData

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully states that the borrow limit is expressed in USD and that querying all assets is possible. However, it does not describe the return format, pagination, authentication needs, or rate limits. This adds some context but is not deeply transparent about the tool's full behavior.

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 long, with the main purpose front-loaded and the optional filtering behavior stated concisely. Every sentence contributes useful information without redundancy or filler.

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 read-only query tool with three optional parameters and no output schema, the description covers the essential aspects: what it retrieves, the USD denomination of limits, and the filtering option. It does not describe the response structure, but given the schema fully documents the parameters and this is a simple data retrieval, the description is sufficiently complete. It slightly misses potential nuances like VIP level impact, but the schema captures the default behavior.

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 each parameter described in the input schema. The description adds a meaningful note about leaving the asset field empty to query all available assets, which clarifies the loanCoin parameter. However, it does not elaborate further on the meaning or expected values of vipLevel or recvWindow beyond what the schema already provides. Baseline of 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?

The description uses a specific verb 'Retrieves' and clearly identifies the resource: 'interest rates and borrowing limits for loanable assets.' It also notes the borrow limit is in USD and offers filtering, which helps clarify scope. However, it does not explicitly distinguish itself from related sibling tools like BinanceGetBorrowInterestRate, though the resource name 'loanable assets' is fairly unique.

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: use this tool to fetch loanable asset data, optionally filtered by specific assets. It does not explicitly state when to use it instead of alternatives, nor does it mention any exclusions or prerequisites. The guidance 'leave it empty to query all available assets' gives some context for when to use the optional parameter, but no broader selection guidance is provided.

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