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 mentions the tool 'Shows how many orders you can place within each interval,' which implies a read-only operation, but does not disclose behavioral traits like authentication requirements, rate limits on the tool itself, error conditions, or response format. This leaves significant gaps for a tool that likely requires API access.

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 that are front-loaded with the main purpose. Every word earns its place by specifying what is retrieved and the scope, with no redundant or vague language, making it highly efficient and well-structured.

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 financial API tool with no annotations and no output schema, the description is incomplete. It lacks details on authentication, response structure, error handling, and how the rate limit data is formatted, which are critical for an AI agent to use the tool effectively 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 input schema has 1 parameter with 100% description coverage, so the baseline is 3. The description adds no parameter-specific information, but since there is only one optional parameter (recvWindow), the tool's core functionality is clear without it. This slight compensation raises the score, as the description effectively conveys the tool's purpose independent of parameters.

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' and the resource 'current trade order count rate limits for all time intervals', specifying exactly what the tool retrieves. It distinguishes from siblings by focusing on rate limits rather than account info, trades, orders, or other Binance US operations, making its purpose specific and unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as authentication needs, or compare it to other tools for rate limit information, leaving the agent without context for selection among the many sibling tools.

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