getSpotMarginTradeRepaymentAvailableAmount

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

No annotations provided, but the description discloses it is a read operation (retrieve), applies only to unified accounts, and gives the formula. It does not detail permissions or rate limits, but for a simple query this is acceptable.

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 plus a bullet point. The purpose is front-loaded, and every sentence adds value. No redundancy.

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?

Given no output schema, the description does not describe the return value format. It explains the input and calculation, but an agent would need to infer the output type. Lacks details on response structure or potential errors.

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?

The only parameter 'currency' is not described in the description beyond being for a specific cryptocurrency. With 0% schema coverage, the description partially compensates by referencing 'spot coin' and 'coin borrow amount', but does not explicitly define the parameter's meaning or format.

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 the available amount for repayment in spot margin trading, using a specific verb ('Retrieve') and resource ('available amount'). It distinguishes from siblings like getSpotBorrowQuota by focusing on repayment, not borrowing.

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 states 'Unified account only', indicating when to use this tool. Provides the calculation formula, but does not explicitly contrast with alternative tools (e.g., accountRepay, quickRepayment) or specify when not to use it.

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