BinancePortfolioMarginGetBankruptcyLoanAmount

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only lookup but says nothing about authentication/permissions, whether a zero result means no bankruptcy loan exists, or what the returned amount represents; there is no output schema to fall back on.

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 front-loaded sentence with no filler, though it is arguably too terse for a tool with no annotations and no output schema.

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 parameterless read query this is minimally sufficient, but given the absence of annotations and an output schema, one sentence explaining what the bankruptcy loan amount means and what a typical response contains would materially help an agent interpret the result.

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?

There is a single optional parameter (recvWindow) with 100% schema description coverage, so the schema already explains it fully. The description adds no additional parameter meaning, which is the baseline when schema coverage is high.

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 states a specific verb ('Query') and a specific resource ('portfolio margin bankruptcy loan amount'), which distinguishes it from the mutating sibling BinancePortfolioMarginRepayBankruptcyLoan. It stops short of naming that sibling explicitly, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this versus BinancePortfolioMarginRepayBankruptcyLoan or the other portfolio margin query tools. The read-only nature is implied by 'Query' but never stated as a usage condition.

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