okx_predictions_candles

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

No annotations are provided. The [L:READ] tag hints at read-only behavior, but this is not formal. The description only notes a prerequisite call to agent_catalog, lacking details on data nature, rate limits, or safety.

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 with prefixes). While concise, it is unclear and uses cryptic tags that may not be universally understood, limiting its effectiveness.

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 3 parameters, no output schema, and no annotations, the description fails to explain return values, pagination, or any context about prediction candles. It is inadequate for an agent to use correctly.

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 documents bar, limit, and instId. The description adds no parameter meaning beyond the schema, thus 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 includes [L:READ] and CAT:[预测] suggesting a read operation for predictions, but does not explicitly state that it retrieves candlestick data for prediction markets. The purpose is unclear and requires knowledge of the category system.

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 is provided on when to use this tool versus many sibling tools like okx_get_candles or okx_predictions_orderbook. The instruction to call agent_catalog first is vague and does not clarify usage context.

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