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 performs a withdrawal/settlement action (implying mutation), requires specific API credentials, and involves sending funds externally ('⚠️ This sends funds to your custodial partner!'). It also clarifies the direction of transfer. However, it doesn't mention potential side effects like irreversible transactions, rate limits, or confirmation times.

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 extremely concise and well-structured, with only three sentences plus warning symbols. The first sentence states the purpose, warnings highlight critical requirements and risks, and the final sentence reinforces the action. Every sentence earns its place by adding essential information without redundancy.

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 tool's complexity (financial settlement with external transfer), lack of annotations, and no output schema, the description does a good job covering the core purpose, prerequisites, and risks. However, it lacks details on return values (e.g., confirmation IDs, status), error conditions, or operational constraints like minimum amounts or supported rails, which would be helpful for a mutation tool of this nature.

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%, providing complete parameter documentation. The description adds no specific parameter semantics beyond what's in the schema (e.g., it doesn't explain 'rail' values or 'asset' formats). Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't need to compensate for schema gaps but also doesn't enhance parameter understanding.

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 ('settles (withdraws) assets') and resources involved ('from your Binance.US custodial sub-account to your custody partner's vault'), using precise terminology. It effectively distinguishes this tool from sibling tools like 'binance_us_custodial_wallet_transfer' or 'binance_us_custodial_custodian_transfer' by focusing on settlement to a custodial partner rather than internal transfers.

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 (settling assets to a custodial partner) and includes critical prerequisites ('⚠️ REQUIRES CUSTODIAL SOLUTION API KEY'). However, it doesn't explicitly state when NOT to use it or name specific alternative tools for different scenarios, such as using 'binance_us_custodial_wallet_transfer' for internal wallet transfers instead.

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