okx_get_order_algo

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

No annotations provided. The description only indicates it's a read operation via '[L:READ]' but does not disclose any behavioral traits such as what constitutes an 'algo' order, whether it returns active or historical orders, or any side effects. More context is needed for a mutation-free tool.

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 extremely short but not concise in a helpful way. It uses cryptic tags and a conditional instruction, which is poor structure. The message '请先调用 agent_catalog' could be front-loaded but the overall lack of clarity makes it ineffective.

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 tool has low complexity (1 parameter, no output schema, no nested objects), the description should clarify what an order algo is and what data it returns. It fails to do so, leaving the agent without essential context about the tool's function or output.

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 has one optional parameter 'algoId' described as '策略委托ID' (strategy order ID). Schema coverage is 100%, so the description adds no new meaning beyond the schema. The baseline score of 3 applies.

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 cryptic labels '[L:READ] CAT:[交易]' without defining what the tool does. It says to call 'agent_catalog' first, but doesn't explain the purpose of 'okx_get_order_algo' itself. The name suggests retrieving algorithmic orders, but the description fails to confirm this or provide context.

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 sibling tools. The only usage hint is '请先调用 agent_catalog', which is a prerequisite, not a usage guideline. There is no mention of when to use this vs other order-related tools like 'okx_get_algo_orders' or 'okx_get_order'.

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