BinanceSubAccountTransferToMaster

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

No annotations are supplied, so the description carries the full burden. It does disclose two behavioral traits beyond the schema: the SPOT-only scope and the sub-account-API-key auth requirement. It says nothing about irreversibility, rate limits, or whether funds move instantly, which matters for a fund-moving 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?

Two sentences, zero filler, and the operation is front-loaded ahead of the auth constraint. Nothing is redundant with the title or name.

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 three-parameter transfer with full schema coverage and no output schema, the description covers direction, market scope, and auth prerequisite — enough to invoke correctly. Only the absence of failure-mode or fee context keeps it from a 5.

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 description coverage is 100%, so asset, amount, and recvWindow are already documented in structured data. The description adds no format, precision, minimum, or fee semantics beyond that, so the baseline 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?

The description gives a specific verb+resource+direction: transfer assets from sub-account to master account, scoped to SPOT. That directionality implicitly distinguishes it from BinanceSubAccountTransferToSub, though the sibling is never named.

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?

It states a hard prerequisite (must be called with a sub-account API key), which is genuinely useful selection context. However, it gives no explicit when-to-use vs. BinanceSubAccountTransferToSub or BinanceSubAccountUniversalTransfer, leaving the agent to infer the choice from the direction wording.

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