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 details the response structure, which is helpful. However, it does not mention authentication requirements, rate limits, or error handling, which are important for a financial API tool. The description adds value but lacks comprehensive behavioral 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 front-loaded with the core purpose, followed by response details and parameter guidance. Every sentence adds value: the first states the action, the second clarifies the return, the third lists response fields, and the fourth explains parameter behavior. No wasted words.

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 tool's moderate complexity (read operation with one optional parameter) and no output schema, the description is mostly complete: it explains the purpose, response structure, and parameter semantics. However, it lacks details on authentication, rate limits, or error handling, which are important for API tools. Without annotations, these gaps prevent a perfect score.

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 input schema has 100% description coverage, so the baseline is 3. The description adds semantic context by explaining the effect of the optional 'asset' parameter ('If no asset is specified, returns balances for all staked assets'), which clarifies usage beyond the schema's technical description. This elevates the score above the baseline.

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 ('Get current staking balance') and resource ('for assets on Binance.US'), distinguishing it from sibling tools like 'binance_us_staking_asset_info' or 'binance_us_staking_history' by focusing on current positions rather than informational or historical data.

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 clear context for when to use this tool ('Get current staking balance') and includes usage guidance for the optional parameter ('If no asset is specified, returns balances for all staked assets'). However, it does not explicitly state when not to use it or name alternatives among siblings, such as 'binance_us_staking_asset_info' for asset details or 'binance_us_staking_history' for historical data.

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