okx_get_premium_history

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

No annotations exist, and the description provides no behavioral details such as mutability, rate limits, or what data is returned. The [L:READ] tag implies a read operation, but it's not explicit or informative.

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 very short (one line), which is concise, but it omits essential purpose and usage 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?

Given 2 parameters, no output schema, and a large set of sibling tools, the description fails to explain what premium history is, how it differs from similar endpoints, or what to expect in the response. The dependency on agent_catalog is noted but not elaborated.

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 already describes both parameters (instId and period) with 100% coverage, so the baseline is 3. The description adds no additional meaning beyond what is in the schema.

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 lacks a clear statement of what the tool does. It only provides metadata tags ([L:READ], CAT:[公共]) and an instruction to call agent_catalog first, but no verb or resource indicating that this retrieves premium history data.

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 similar siblings like okx_get_candles or okx_get_funding_rate_history. The instruction to call agent_catalog first is a dependency hint, 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.