Binance.US MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates critical behavioral traits: the tool moves funds (destructive operation), requires specific API key permissions, and includes a warning to verify details. It also explains the purpose of the transfer (enabling trading/settlement). The main gap is lack of information about rate limits, error conditions, or confirmation mechanisms.

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 appropriately sized with three sentences. The warning emojis and capital letters effectively front-load critical information. The second sentence could be slightly more concise, but overall the structure is efficient with zero wasted text.

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 fund transfer tool with no annotations and no output schema, the description provides good contextual completeness. It covers the destructive nature, authentication requirements, and purpose of the operation. The main gap is the lack of information about what the tool returns (success/failure indicators, transaction IDs, etc.), which would be helpful given there's no output schema.

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 schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 specific action ('Transfer assets') and resources involved ('from your Binance.US exchange wallet to your custodial sub-account'). It distinguishes this tool from sibling tools like 'binance_us_custodial_balance' (which reads balances) and 'binance_us_custodial_custodian_transfer' (which transfers to custodial partners rather than sub-accounts).

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 provides clear context about when to use this tool (transferring assets to custodial sub-accounts for trading/settlement) and includes important prerequisites (requires custodial solution API key). However, it doesn't explicitly state when NOT to use it or name specific alternative tools for different transfer scenarios.

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