okx_get_history_trades

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

With no annotations, the description must disclose behavioral traits. It includes a '[L:READ]' tag implying read-only, but provides no further details about what data is returned, limitations, or side effects. The prerequisite is vague and doesn't help understand behavior.

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 at the cost of substance. It is not helpful for an agent to select or invoke the tool correctly. True conciseness would preserve essential information without verbosity.

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, the description fails to differentiate this tool. It does not explain what history trades are, how they differ from other trade endpoints, or provide any usage context. No output schema further limits completeness.

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%, so the schema already describes the two parameters (instId, limit) with descriptions. The description adds nothing beyond what the schema provides, 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 fails to state what the tool does. It only provides a category label and a prerequisite ('请先调用 agent_catalog'), leaving the actual purpose unclear. This is a tautology of the name combined with an instruction, not a description of the tool's 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?

There is no guidance on when to use this tool versus alternatives like okx_get_trades or okx_get_history_candles. The description only instructs to call agent_catalog first, which is a prerequisite, not a usage guideline.

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