okx_get_easy_convert_history

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

The description includes '[L:READ]' indicating a read operation, but this is not an annotation and is the only behavioral hint. Beyond that, no details about side effects, rate limits, data refresh rate, or other traits are disclosed. With no annotations, the description carries the full burden and is insufficient.

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 (one line) and while technically concise, it sacrifices clarity and completeness. It fails to provide essential information, making it under-specified rather than efficiently concise.

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 tool with 3 optional parameters, no output schema, and many siblings, the description is woefully incomplete. It does not explain what the history contains, how to interpret parameters, or what the response looks like. The prerequisite instruction alone is insufficient.

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 all three parameters (after, limit, before) described in Chinese. The description adds no additional semantic information beyond what the schema already provides, so baseline 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 is vague and cryptic, using a category label and a prerequisite instruction ('→ 请先调用 agent_catalog') instead of explicitly stating the tool's purpose. The name suggests it retrieves history of easy convert operations, but the description fails to confirm this or provide a clear verb-resource statement.

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?

The only guidance is a prerequisite to call agent_catalog first, but there is no advice on when to use this tool versus alternatives like okx_get_easy_convert_currency_list or okx_easy_convert. No exclusions or context for selection are provided.

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