okx_get_candles

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It mentions a limit of 300 candles but does not clarify read-only status, return format, ordering, or any rate limits. 'Fetch' implies read-only, but the description lacks explicit caveats or additional context.

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 two concise sentences with no fluff. Every word contributes: the action, the resource, the use case, and the return cap. It is well-structured and immediately readable.

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?

With no output schema and no annotations, the description should describe the return structure and clarify the meaning of instType and instrument. It only states 'OHLCV candle data' and the maximum count, leaving the agent to guess the exact fields, ordering, and instrument semantics. This is insufficient for a tool with four parameters.

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 only 50%, with instType and instrument lacking descriptions. The description adds no detail about these parameters and merely restates the limit maximum already present in the schema. It fails to compensate for the undocumented parameters, providing minimal added meaning.

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 uses a specific verb 'Fetch' and resource 'OHLCV candle data' with a clear purpose 'for chart analysis'. This distinguishes it from sibling tools like okx_get_ticker and okx_technical_analysis, which target different data types or analyses.

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?

The description hints at usage context with 'for chart analysis' but does not explicitly state when to use this tool over alternatives like okx_get_market_data or okx_get_ticker. There is no mention of exclusions or when not to use it, leaving only implied guidance.

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