binance_get_convert_quote

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

Annotations provide readOnlyHint=true and destructiveHint=false, and the description is consistent, adding that it 'moves no funds' and nothing is converted until accepted. It goes well beyond the annotations by disclosing the UID weight 200 rate cost, that it works with the trading kill-switch off, that a quote is a short-lived non-idempotent reservation (not free, do not poll in a loop), and that the quoteId becomes void after validTimestamp — all of which align with openWorldHint=true and idempotentHint=false.

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?

Roughly 230 words is long, but every sentence earns its place given the reservation semantics, rate-weight, kill-switch nuance, and error codes that the description must carry at 0% schema coverage. It is front-loaded with the core purpose and behavioral headline, then uses clear labeled sections (When to Use, When NOT to Use, Returns, Examples, Error Handling) that make it scannable rather than a wall of prose.

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?

The description covers the full call lifecycle: endpoint and signing, cost/weight, the allowlist quirk, the quote's expiry and invalidation, the accept step, return fields, example inputs, and the three most relevant Binance error codes. Even though an output schema exists (so return values needn't be explained), it describes the quoteId/ratio/inverseRatio/validTimestamp result anyway, making the tool callable correctly with zero prior Binance knowledge.

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?

With schema description coverage reported at 0%, the description carries the parameter-semantics burden and largely succeeds: two full example param sets illustrate the exactly-one-of from_amount/to_amount decision and the valid_time format, and the Error Handling section ties failure codes to amount precision and pair limits. Minor gaps remain — wallet_type and response_format are not explained in the description text — but the core parameters an agent must get right are well covered.

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 opens with a specific verb+resource: 'Request a convert quote: a reserved ratio, valid for 10 s to 2 minutes', and names the exact endpoint `POST /sapi/v1/convert/getQuote`. It actively distinguishes itself from siblings — noting it is NOT for indicative prices (binance_get_ticker_price) and NOT for converting at unavailable prices (binance_place_convert_limit_order) — so an agent can separate it from the other convert/order tools without opening schemas.

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?

Explicit 'When to Use' and 'When NOT to Use' sections name sibling tools and the conditions selecting them: binance_get_ticker_price for free indicative prices, binance_place_convert_limit_order for unavailable prices, and binance_accept_convert_quote as the mandatory second half of the flow. This leaves nothing to inference about when to invoke this tool versus any alternative.

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