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 requires institutional agreements, affects LTV ratios (with specific directional impacts), has financial risk implications, and includes status responses (SUCCESS, PENDING, FAILED). It doesn't cover rate limits or authentication details, but provides substantial risk context.

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 clear sections (warnings, prerequisites, transfer types, response format) and uses bullet points effectively. While comprehensive, it could be slightly more concise by combining some warning elements, but every sentence adds value for this high-risk financial operation.

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 high-risk financial transfer tool with no annotations and no output schema, the description provides substantial context: risk warnings, prerequisites, transfer type explanations, and response format details. It doesn't cover authentication or rate limits, but given the schema's completeness and the tool's complexity, it provides adequate guidance for safe usage.

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 adds some context about transfer types (TRANSFER_IN adds collateral, TRANSFER_OUT withdraws) which complements but doesn't significantly expand beyond the schema's parameter descriptions. This meets the baseline for high schema coverage.

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 a transfer') and target resource ('in or out of the credit line account'), distinguishing it from sibling tools like 'binance_us_cl_account' (info) and 'binance_us_cl_transfer_history' (history). It goes beyond the name/title by specifying the directionality 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 explicit guidance on when to use this tool (for credit line transfers) and when not to use it (requires institutional credit line agreement). It includes prerequisites (checking LTV ratio, available amounts) and distinguishes from alternatives by focusing on credit line operations rather than regular account transfers.

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