BinanceSubAccountUniversalTransfer

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

No annotations exist, and the description carries the full burden. It never discloses that this is an irreversible fund movement, that it requires authenticated sub-account or master permissions, that it may be subject to transfer rate limits, or that the response confirms a transaction ID. Only the implication of the word 'transfer' signals mutation.

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?

It consists of one tightly worded sentence with no filler, and the transfer direction is front-loaded. However, the brevity comes at the cost of the details an agent needs before moving funds.

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 an 8-parameter, unannotated, irreversible fund-movement tool with no output schema, the description does almost nothing to explain required permissions, email semantics, or failure behavior. It is far thinner than the tool's risk complexity level warrants.

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%, so the schema already explains asset, amount, account types, email fields, the ISOLATED_MARGIN symbol rule, and recvWindow. The description adds no ambiguity resolution or usage nuance beyond that, so the baseline of 3 applies.

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?

'Universal transfer' gives a specific verb-plus-resource, and the sentence names the two endpoint pairs (sub-to-sub and master-to-sub). The wording is clear, but it doesn't distinguish this tool from very close siblings such as BinanceSubAccountTransferToSub, BinanceSubAccountTransferToMaster and BinanceWalletUserUniversalTransfer.

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 about when to call this tool rather than the one-directional transfer siblings, or when to use it rather than BinanceWalletUserUniversalTransfer. It also omits prerequisites such as requiring a sub-account API key or the master-account email convention.

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