BinanceConvertOrderStatus

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

With no annotations, the description carries full responsibility. It implies a read-only operation and lists the return fields (conversion status, assets, amounts, exchange rate, creation time), but it does not explicitly disclose side effects (or their absence), error conditions, or any constraints beyond the parameter mutual exclusivity.

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 a single, focused sentence, front-loaded with the verb and resource, and includes a concise enumeration of the key return fields. No unnecessary words or repetition.

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 simple status-check tool with two parameters and no output schema, the description adequately covers purpose, parameter relationship (via schema), and return values. It does not mention how to obtain an orderId/quoteId or handle errors, but those are not essential for correct invocation.

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 coverage is 100% and each parameter already states 'either this or the other is required'. The description merely repeats the 'either orderId or quoteId' relationship without adding new meaning, so it adds no value beyond the structured parameter data.

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 specifies the exact action ('checks the status') and resource ('token conversion order'), and clarifies it uses orderId or quoteId. This clearly distinguishes it from sibling tools like BinanceGetOrder (for regular orders) and other BinanceConvert tools for creating or accepting quotes.

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?

Usage context is implied ('checks status of a conversion order'), but the description does not explicitly state when to use this tool versus alternatives like BinanceGetOrder, nor does it mention any exclusions or prerequisites. The 'when-to-use' guidance is minimal.

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