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 describes what information is returned but doesn't disclose behavioral aspects like whether this is a read-only operation (implied by 'Get' but not explicit), authentication requirements, rate limits, pagination, or error conditions. For a tool with no annotation coverage, this represents a significant gap in behavioral disclosure.

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 with zero wasted words. The first sentence establishes the core purpose and key details, while the second adds important supplementary information about network-specific status. Every element earns its place, and the structure is front-loaded with the most critical information.

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?

For a read operation with one optional parameter and no output schema, the description adequately covers what information is returned. However, without annotations or output schema, it lacks details about return format, authentication needs, rate limits, or error handling. The description is complete enough for basic understanding but leaves important operational context unspecified.

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% with one optional parameter 'recvWindow' fully documented in the schema. The description doesn't mention any parameters or add semantic context beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate since 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 details' and specifies the resource 'all crypto assets', with explicit details about what information is included: 'fees, withdrawal limits, and network status' plus 'deposit/withdrawal enabled status per network'. It distinguishes from sibling tools like 'binance_us_exchange_info' or 'binance_us_custodial_supported_assets' by focusing specifically on asset-level configuration details rather than general exchange info or custodial assets.

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 context by specifying what details are retrieved (asset configuration), but doesn't explicitly state when to use this tool versus alternatives like 'binance_us_exchange_info' (which might include broader exchange metadata) or 'binance_us_custodial_supported_assets' (which focuses on custodial services). No explicit 'when-not' guidance or prerequisite information is provided.

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