okx_get_order_by_clOrdId

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

No annotations are provided, and the description only includes a cryptic label 'L:READ' without explaining behavioral traits such as side effects, permissions, or rate limits. The agent is left without essential context for safe invocation.

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 very short but also uninformative and cryptic. Conciseness alone does not justify a higher score because the content is not useful for an agent to understand the tool.

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?

Given the large number of sibling tools, lack of output schema, and absence of annotations, the description is severely incomplete. It fails to provide any information about return values, error handling, or usage context.

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 fully describes the two required parameters (instId and clOrdId) with Chinese descriptions. The tool description adds no additional meaning beyond what the schema provides. With 100% schema coverage, a baseline of 3 is appropriate.

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 '[L:READ] CAT:[交易] | → 请先调用 agent_catalog' is cryptic and does not clearly state the tool's function. The name suggests retrieving an order by client order ID, but the description fails to explicitly state this, making it difficult for an agent to understand its purpose.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list includes many order-related tools (e.g., okx_get_order, okx_get_orders_pending), and the description provides no differentiation or context for selection.

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