okx_get_call_auction_details

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

With no annotations provided, the description must disclose behavioral traits. It offers none—no mention of read-only status, rate limits, authentication requirements, or side effects. The cryptic '[L:READ]' might imply read-only but is not explained.

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?

While short, the description is poorly structured. The use of bracket codes and Chinese text without translation or explanation makes it less concise and harder to parse. The instruction to call agent_catalog is misplaced and disrupts clarity.

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 tool with one parameter, the description should explain what 'call auction details' are and why agent_catalog is a prerequisite. It does neither, leaving the agent without enough context to understand when and how to use it effectively.

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 provides 100% coverage for the single parameter 'instId' with a clear description. The tool description adds no additional semantic meaning beyond the schema, so a baseline score 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 uses cryptic codes like '[L:READ]' and 'CAT:[公共]' without explaining the tool's purpose. It references 'call auction details' in the name but fails to clarify what that means. The instruction to call agent_catalog first hints at a prerequisite but obscures the core function.

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 explicit guidance on when to use this tool versus any sibling. The only usage hint is '请先调用 agent_catalog', which implies a prerequisite but does not explain why one would need this tool over alternatives like okx_get_ticker or okx_get_orderbook.

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