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 locking of assets ('Staking locks your assets for a period of time'), the need for balance verification, and the default behavior for autoRestake. However, it does not mention potential errors, rate limits, or authentication requirements, which are common for financial operations.

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, starting with the core purpose, followed by important warnings, parameter details, and response information. Every sentence serves a clear purpose, with no redundant or unnecessary content, making it efficient and easy to parse.

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 staking operation (financial, with locking periods) and the absence of annotations and output schema, the description does a good job covering key aspects: purpose, prerequisites, parameters, and response structure. However, it lacks details on error handling, rate limits, or specific authentication needs, which are important for a complete understanding in this 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?

The schema description coverage is 100%, so the baseline is 3. The description adds value by providing context for each parameter: it explains that 'stakingAsset' refers to supported assets (e.g., BNB, ETH), clarifies the purpose of 'amount' in the staking context, and notes the default behavior for 'autoRestake'. This enhances understanding beyond the schema's technical definitions.

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 ('Stake a supported asset') and resource ('on Binance.US') with the explicit goal ('to earn staking rewards'). It distinguishes itself from siblings like 'binance_us_staking_asset_info' or 'binance_us_staking_unstake' by focusing on the staking operation itself.

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, including prerequisites ('Check unstakingPeriod using binance_us_staking_asset_info before staking', 'Ensure you have sufficient balance', 'Verify min/max staking limits') and references to alternative tools (e.g., 'binance_us_staking_asset_info'). This helps the agent understand the proper context and conditions for invocation.

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