okx_get_candles

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

No annotations provided, so description must disclose behavior. It only gives a category and a prerequisite, omitting traits like data freshness, pagination, rate limits, or effects. Virtually no behavioral information.

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 short but inefficient, using cryptic tags (L:READ, CAT:[行情]) and a prerequisite note. It could be more concise and directly state the tool's purpose. Not every sentence earns its place.

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?

Despite low complexity (3 params, no output schema), the description is severely incomplete. It does not explain the return format, when to use this vs history candles, or any context. The prerequisite instruction is unhelpful without further elaboration.

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% with descriptions for all three parameters (bar, limit, instId). The description adds no additional meaning beyond the schema. Baseline score of 3 applies per guidelines.

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 is vague: '[L:READ] CAT:[行情] | → 请先调用 agent_catalog'. It labels it as read and market data category but does not state 'Get candles' or specify the action. The name implies OHLCV data, but the description itself lacks a clear verb+resource statement. No differentiation from sibling tools like okx_get_history_candles.

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 usage guidance provided. The instruction to call agent_catalog first is a prerequisite, not a guideline on when to use this tool versus alternatives. No mention of scenarios or exclusions.

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