Binance.US MCP Server

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

With no annotations provided, the description carries full burden. It discloses the API key requirement (important auth context) and lists response fields, which helps understand what to expect. However, it doesn't mention potential side effects, rate limits, error conditions, or whether this is a synchronous/asynchronous operation.

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 well-structured with a clear purpose statement up front, important warning, usage context, and response format. Every sentence serves a purpose. It could be slightly more concise by combining some of the response field explanations.

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 financial transfer tool with no annotations and no output schema, the description provides reasonable coverage of purpose, usage, and response format. However, it lacks important contextual details like error handling, confirmation requirements, settlement time, or whether this is an irreversible operation.

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 the schema already fully documents all 4 parameters. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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'), source ('from Binance.US exchange wallet'), and destination ('to custodial sub-account'). It distinguishes itself from sibling tools like 'binance_us_custodial_wallet_transfer' by specifying the direction of transfer (exchange to custodial).

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 for when to use this tool ('to move assets from your Binance.US exchange wallet to your custodial sub-account for trading') and mentions the API key requirement. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the many sibling tools.

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