get_convert_order_status

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

No annotations are provided, so the description carries the full burden. It states the action but does not disclose behavioral details such as read-only nature, what happens if neither or both identifiers are provided, required permissions, or potential error cases. This is a significant gap for a tool with two optional parameters.

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 12-word sentence that is front-loaded with the verb and resource. It contains no filler, making it extremely concise and well-structured.

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 tool is simple with two optional parameters and no output schema. The description does not clarify whether at least one identifier is required, nor does it describe the return format or error behavior. However, given the simplicity, the basic purpose is clear, but completeness is limited.

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?

The schema already provides descriptions for both orderId and quoteId, achieving 100% coverage. The description's mention of 'by orderId or quoteId' adds a minor note about interchangeability but does not add substantial meaning beyond the schema.

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 uses the specific verb 'Check' and identifies the exact resource: 'status of a Binance Convert order' with two lookup identifiers. This clearly distinguishes it from sibling tools like get_convert_quote (get a quote) and get_convert_trade_history (list trade history).

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 implies usage for checking the status of a specific convert order after placing it, but does not explicitly mention when to choose this over alternatives such as get_convert_trade_history or accept_convert_quote. No exclusions or alternative mentions are present.

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