Binance.US MCP Server

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: the API key requirement ('REQUIRES CUSTODIAL SOLUTION API KEY'), performance implications ('can be slow'), and response format details. However, it doesn't mention pagination, rate limits, or error conditions that would be helpful for a production tool.

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 appropriately sized and front-loaded with the core purpose. The warning emojis and response format details are useful but could be more structured. Every sentence earns its place, though the response format listing could be more concise.

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 no output schema, the description provides good context: purpose, prerequisites, usage warnings, and response format. It covers the essential information an agent needs, though additional details about error handling or rate limits would make it more complete for a financial API tool.

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 thoroughly. The description adds marginal value by emphasizing the 'symbol' parameter recommendation ('Recommended to always specify') and warning about performance without it, but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 ('Get all open custodial trade orders') with the resource type specified. It distinguishes itself from sibling tools like 'binance_us_open_orders' (non-custodial) and 'binance_us_cust_get_order' (gets a specific order) by specifying 'custodial' scope and 'all open' nature.

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 explicit guidance on when to use ('Get all open custodial trade orders') and when not to use ('Do not call without a symbol parameter as it returns all pairs and can be slow'). It also implicitly distinguishes from alternatives by specifying the custodial nature versus non-custodial sibling tools.

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