BinanceGetOrder

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

No annotations are present, so the description carries the burden. 'Check status' implies a read operation, but the description does not disclose whether it modifies anything, whether an order ID is required, or what happens for nonexistent orders. It is minimal but not misleading.

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?

One sentence, directly states the action and scope, with no filler or unnecessary words.

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 read tool, the description conveys the core purpose, but it omits the practical need for at least one order identifier (orderId or origClientOrderId) and any return details. Since there is no output schema, a bit more context would help an agent invokes it correctly.

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 input schema covers all three parameters with descriptions, so the baseline is 3. The description only adds that the symbol is a trading pair, which largely repeats schema information; the need for either orderId or origClientOrderId is not clarified.

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 a specific verb 'Check' and identifies the resource as an order on Binance, scoped to a trading pair. It distinguishes from list-oriented siblings by focusing on a single order's status, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus siblings like BinanceAllOrders, BinanceGetOpenOrders, or BinanceGetTrades. The context of checking a single order's status is implied, but no when/why or exclusions are given.

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