Binance.US MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and adds valuable behavioral context: it discloses rate limit implications (weight 40 vs 3) for unfiltered queries, which is critical for API usage. However, it lacks details on authentication needs, pagination, 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?

Two sentences with zero waste: the first states the purpose and filtering capability, the second warns about rate limits. It is front-loaded and appropriately sized for the tool's complexity.

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 no annotations and no output schema, the description is fairly complete for a read operation, covering purpose, filtering, and rate limits. However, it could improve by mentioning authentication requirements or response format, though the lack of output schema is not its fault.

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 adds marginal value by explaining the symbol filter's purpose and rate limit impact, but does not provide additional syntax or format details beyond what the schema offers.

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 resource 'all open orders on Binance.US', specifying it can be filtered by symbol. It distinguishes from siblings like 'binance_us_all_orders' (historical) and 'binance_us_cust_open_orders' (custodial) by focusing on current open orders, though not explicitly named.

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?

It provides clear context for when to use symbol filtering (to reduce rate limit impact) but does not explicitly mention when not to use this tool versus alternatives like 'binance_us_cust_open_orders' for custodial orders or 'binance_us_all_orders' for historical data.

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