okx_get_history_index_candles

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

No annotations provided, and description only hints at 'READ' (suggesting idempotency) but fails to disclose behavioral traits such as permission requirements, rate limits, or side effects. The description carries the full burden but offers minimal insight.

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 under-specified and cryptic, omitting essential information. It is not concise in a useful sense; brevity without clarity is a drawback.

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 tool has 5 parameters, no output schema, and no annotations, the description is completely inadequate. It fails to explain return values, pagination behavior, or any other contextual details needed for correct usage.

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 description coverage is 100%, so the input schema fully documents parameters. The description adds no additional meaning beyond what is already in the schema, so 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?

Description provides a cryptic header '[L:READ] CAT:[行情]' and instruction to call agent_catalog first, but does not clearly state the tool's action (retrieve historical index candles) or provide a meaningful verb-resource pair. The purpose is vague and requires inference.

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_index_candles or okx_get_history_candles. The instruction to call agent_catalog is unclear and does not help with decision-making.

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