Binance.US MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that this is a read operation ('Get') and describes the return content, but doesn't mention authentication requirements, rate limits, or potential errors. For a financial API tool with no annotation coverage, this leaves significant behavioral gaps regarding security and operational constraints.

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 two sentences with zero waste. The first sentence states the purpose and scope, while the second elaborates on return details. Every word contributes to understanding the tool's function without redundancy or unnecessary elaboration.

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 no annotations, no output schema, and a simple single-parameter input schema, the description provides adequate basic information about what the tool returns. However, for a financial account tool, it lacks details about authentication requirements, error handling, or data freshness that would be helpful for an AI agent. The description is complete enough for basic usage but has notable gaps in operational context.

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% for the single parameter 'recvWindow', which is fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 where the schema handles parameter documentation adequately.

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 verb ('Get') and resource ('current account information') with specific details about what's included ('balances and permissions', 'all asset balances (free and locked), account permissions, and trading status'). It distinguishes itself from sibling tools like 'binance_us_cust_balance' or 'binance_us_subaccount_assets' by focusing on comprehensive account-level data rather than specific subsets or subaccount information.

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 implies usage for retrieving account-level information but doesn't explicitly state when to use this tool versus alternatives like 'binance_us_cust_balance' (custodial balance) or 'binance_us_subaccount_assets' (subaccount assets). It provides context about what data is returned but lacks explicit guidance on prerequisites or exclusions.

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