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 the tool retrieves current fee rates based on VIP level and notes that BNB discounts are excluded, adding useful context. However, it does not cover other behavioral aspects like authentication requirements, rate limits, or error handling, leaving gaps for a tool likely requiring user-specific data.

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 concise and front-loaded, consisting of two sentences that directly state the tool's function and a key limitation. Every sentence adds value without redundancy, making it efficient and easy to understand.

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 (retrieving user-specific fee data) and no annotations or output schema, the description is somewhat complete but lacks details on authentication, response format, or error cases. It covers the core purpose and a limitation, but additional context would improve usability for 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 both parameters. The description does not add specific parameter details beyond what the schema provides, but it implicitly clarifies the context for the 'symbol' parameter by mentioning 'spot trading' and 'all symbols', offering slight semantic enhancement. With zero required parameters, this meets the baseline expectation.

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 tool's purpose with specific verbs ('Get') and resources ('maker & taker fee rates for spot trading'), and distinguishes it from siblings by focusing on fee rates based on VIP level. It explicitly mentions what is not included (BNB fee discount), which helps differentiate it from potential alternatives.

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 checking fee rates in spot trading, but does not explicitly state when to use this tool versus alternatives (e.g., other fee-related tools or general account info). It mentions a specific limitation (BNB discount not factored), which provides some context, but lacks clear guidance on scenarios or prerequisites for use.

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