okx_get_index_candles

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

No annotations are provided, and the description does not disclose behavioral traits such as data retur ned, pagination, rate limits, or any side effects. The '[L:READ]' prefix hints at read-only but is not elaborated.

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 lacks informative content. It is underspecified rather than concise, failing to convey necessary details in an efficient manner.

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 presence of many similar sibling tools (e.g., okx_get_candles, okx_get_history_index_candles), 5 parameters, and no output schema, the description is completely inadequate. It does not specify what the tool does, how it differs, or what the return format is.

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 defines parameters. The description does not add any extra meaning beyond what is in the schema, meeting the baseline for high coverage.

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 only provides a category label '[L:READ] CAT:[行情]' and a reference to call agent_catalog, but does not explicitly state that the tool retrieves index candles. The purpose is implied by the name, but the description adds little clarity.

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 alternatives like okx_get_candles or okx_get_history_index_candles. The instruction to call agent_catalog first is ambiguous and 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.