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 warns '⚠️ This moves funds between accounts!', indicating a destructive operation, which is helpful. However, it lacks critical details such as authentication requirements, rate limits, whether the transfer is reversible, confirmation steps, or error handling, leaving significant gaps for a financial transaction 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 front-loaded with the core purpose in the first sentence and includes a warning in the second. It's efficient with two sentences, though the warning could be more specific (e.g., 'irreversible' or 'requires 2FA'). No wasted words, but slight room for improvement in clarity.

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 complexity of a financial transfer tool with no annotations and no output schema, the description is insufficient. It lacks details on authentication, security measures (e.g., 2FA), transfer limits, response format, error cases, and idempotency. The warning is a start, but more context is needed for safe and effective use.

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 fully documents all 5 parameters. The description adds no additional parameter semantics beyond what the schema provides (e.g., it doesn't clarify email formats, asset symbol constraints, or amount precision). The baseline score of 3 is appropriate since the schema does the heavy lifting.

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 ('Execute an asset transfer') and the resources involved ('between master account and a sub-account'). It distinguishes itself from sibling tools like 'binance_us_subaccount_assets' (which retrieves assets) and 'binance_us_subaccount_transfer_history' (which retrieves history) by focusing on the execution of 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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication requirements), nor does it differentiate from similar tools like 'binance_us_custodial_custodian_transfer' or 'binance_us_cust_transfer', leaving the agent to infer usage context from tool names alone.

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