okx_predictions_get_order

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

No annotations provided; '[L:READ]' is an informal hint but not a standard annotation. Description does not disclose side effects, authorization needs, or rate limits.

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?

Description is very short but cryptic; the prerequisite note is front-loaded but unclear. Could be more concise and 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?

No output schema and description does not explain what the tool returns or how to interpret results. Incomplete for a get-order operation.

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 has 100% coverage for orderId with description '订单ID（必填）', so schema adequately explains the parameter. Description adds no extra meaning.

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?

Description is vague; 'L:READ' and 'CAT:[预测]' hint at read-only predictions but do not clearly state the tool retrieves an order. The name implies it, but description lacks explicit verb and resource.

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?

Only mentions prerequisite to call agent_catalog first, but provides no guidance on when to use this tool vs alternative prediction tools (e.g., okx_predictions_order_list).

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