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 of behavioral disclosure. It effectively explains key traits: the tool is for requesting quotes (not executing trades), quotes expire based on 'validTimestamp', and it requires quick use. This covers critical operational behavior, though it could add details like rate limits or authentication needs for completeness.

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 well-structured with a clear opening sentence, important warnings highlighted, and organized sections for parameters and response. It avoids redundancy, but the parameter list slightly repeats schema information, and the response details could be more concise given the lack of an output schema.

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 moderate complexity (4 parameters, no annotations, no output schema), the description is mostly complete. It explains the tool's purpose, usage context, behavioral traits, and response format. However, it lacks details on error handling or authentication requirements, which would enhance completeness 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 all parameters fully. The description lists parameters and provides examples (e.g., 'BTC, SHIB'), but adds minimal semantic value beyond the schema. This meets the baseline for high schema coverage, where the description doesn't need to compensate heavily.

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 ('Request a quote for an OTC trade') and resource ('on Binance.US'), with the first sentence providing a concise overview. It distinguishes this tool from siblings like 'binance_us_otc_place_order' by focusing on quote retrieval rather than order execution, making the purpose 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 clear context for when to use this tool—to get a price quote before placing an OTC trade—and warns about quote expiration, which is crucial timing guidance. However, it does not explicitly mention when not to use it or name alternatives like 'binance_us_otc_place_order' for actual trading, leaving some room for improvement in sibling differentiation.

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