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. It effectively discloses key behavioral traits: it's a read-only check (implied by 'Check'), requires authentication ('Requires API key authentication'), and defines the return format (status codes 0 and 1). This covers essential aspects like operation type and auth needs, though it lacks details on rate limits or error handling.

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 perfectly concise and front-loaded: it states the core purpose in the first clause, adds critical status code details, and ends with authentication requirements. Every sentence earns its place with no wasted words, making it highly efficient.

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 low complexity (0 parameters, no output schema, no annotations), the description is largely complete. It explains what the tool does, the return format, and authentication needs. However, without an output schema, it could benefit from clarifying the exact structure of the response (e.g., JSON format), though the status codes provide sufficient guidance for basic use.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the inputs. The description adds no parameter information, which is appropriate. Baseline is 4 for 0 parameters, as there's nothing to compensate for, and the description doesn't need to cover params.

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 ('Check if Binance.US system is under maintenance') and resource ('Binance.US system'), distinguishing it from siblings that focus on trading, account management, or other operations. It provides precise status codes (0=normal, 1=maintenance), making the purpose unambiguous and 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 context by mentioning 'Requires API key authentication,' suggesting it's for authenticated system status checks. However, it doesn't explicitly state when to use this tool versus alternatives like 'binance_us_ping' or 'binance_us_server_time' for system availability, leaving some ambiguity.

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