getSpotMarginTradeMaxBorrowable

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

No annotations are provided, so the description carries the full burden. It states 'Retrieve' to indicate a read operation but does not disclose any potential side effects, auth requirements, rate limits, or how the borrowable amount is determined.

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 lines: first line states the purpose, second line adds a constraint. It is concise, front-loaded, and contains no redundant 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?

Given the simplicity (single parameter, no output schema), the description covers the essential purpose and a key constraint. However, it lacks details on what factors influence the result or the format of the return value.

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 description mentions 'specified cryptocurrency' which refers to the 'currency' parameter, but schema coverage is 0%. The description adds minimal meaning beyond the parameter name, lacking details on format or allowed values.

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 verb 'Retrieve' and the resource 'maximum borrowable amount for a specified cryptocurrency in spot margin trading'. It also includes a specific constraint 'Unified account only', distinguishing it from sibling tools like getSpotBorrowQuota.

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 explicitly mentions 'Unified account only', setting a clear precondition. It does not, however, specify when not to use this tool or compare it with alternatives like getSpotBorrowQuota.

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