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: it is a write/mutation operation (implied by 'Transfer'), requires specific authentication ('CUSTODIAL SOLUTION API KEY'), and describes the response structure. However, it lacks details on error conditions, rate limits, or idempotency, which would be helpful for a financial transfer tool.

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 and front-loaded with the core purpose, followed by essential warnings and usage context, then response details. Every sentence earns its place—no fluff or redundancy. It is appropriately sized for a tool with authentication requirements and a detailed response.

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 transfer with authentication needs) and the absence of annotations and output schema, the description does a good job covering purpose, prerequisites, usage, and response format. However, it could be more complete by addressing potential errors, idempotency, or rate limits, which are important for such operations.

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 documents all parameters thoroughly. The description does not add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't explain 'rail' options or 'asset' constraints further). Baseline 3 is appropriate as the schema does the heavy lifting, but no extra value is added.

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 custodial partner account to Binance.US custodial sub-account'), distinguishing it from sibling tools like 'binance_us_cust_wallet_transfer' or 'binance_us_subaccount_transfer' which involve different transfer types. The purpose is precise and unambiguous.

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 explicit context for when to use this tool ('to move assets from your custodial partner... to your Binance.US custodial sub-account for trading') and mentions a prerequisite ('REQUIRES CUSTODIAL SOLUTION API KEY'). However, it does not explicitly state when NOT to use it or name specific alternative tools for different transfer scenarios, though the context implies differentiation from other transfer-related siblings.

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