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 full burden. It states the tool 'Get[s] a deposit address' but doesn't disclose behavioral traits like whether this requires authentication, if it's idempotent, rate limits, or what the return format is (e.g., address string, network details). For a financial tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 concise sentences that are front-loaded with the core purpose and usage. Every word earns its place, with no redundancy or fluff, making it easy to parse quickly.

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 deposit tool with no annotations and no output schema, the description is incomplete. It lacks details on authentication needs, error handling, return values, or any behavioral constraints. While concise, it doesn't provide enough context for safe and effective use by an AI agent.

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 (coin, network, recvWindow) with descriptions. The description adds no additional parameter semantics beyond implying 'crypto asset' relates to 'coin' and 'network'. Baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate with extra context like format examples or dependencies.

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 action ('Get a deposit address') and target resource ('for a specific crypto asset'), with the purpose of receiving funds into a Binance.US account. It doesn't explicitly differentiate from sibling tools like 'binance_us_withdraw_crypto' or 'binance_us_deposit_history', but the verb 'Get' and context of receiving funds make its role reasonably distinct.

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 when needing to receive funds into a Binance.US account, but provides no explicit guidance on when to use this versus alternatives (e.g., vs. checking deposit history or withdrawing). It mentions the purpose ('to receive funds'), which gives some contextual hint, but lacks clear when/when-not statements or named alternatives.

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