okx_get_order

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

No annotations provided, so description carries full burden. It only hints at read-only via '[L:READ]', but does not disclose authentication needs, rate limits, error behavior, or any side effects. For a read operation, basic behavioral details are missing.

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 short but includes non-standard prefixes and a seemingly mandatory prerequisite call, which adds noise and reduces clarity. It is not concise in a helpful way.

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 complexity of the tool ecosystem (many sibling order tools), no output schema, and no annotations, the description is far from complete. It fails to explain return values, error cases, or how this tool fits into the workflow.

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% with clear descriptions for both parameters (ordId and instId). The description adds no further meaning, so baseline 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 includes cryptic tags like '[L:READ] CAT:[交易]' and an instruction to call agent_catalog, but does not clearly state that the tool retrieves a specific order by ID. The name is self-explanatory, but the description adds confusion rather than clarity.

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 on when to use this tool versus other order retrieval tools like okx_get_orders_pending or okx_get_orders_history. The only instruction is to call agent_catalog first, which is a prerequisite but not usage context.

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