okx_get_spread_candles

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

With no annotations, the description must disclose behavior. It only marks the tool as read '[L:READ]' but fails to describe expected behavior, idempotency, rate limits, or the structure of returned data. Schema implies it's a fetch operation, but behavioral details are missing.

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, which is concise, but the content is cryptic (brackets, Chinese arrow). It is not well-structured for an English-speaking agent; the format is confusing and lacks clarity.

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?

No output schema, so description should clarify return format and usage context. It mentions a prerequisite (agent_catalog) but does not explain what agent_catalog provides or how to interpret the candles data. The description is incomplete for an agent to use effectively.

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 baseline is 3. Description does not add any parameter-specific information beyond what the schema already provides. No additional meaning is given.

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 is cryptic, using '[L:READ] CAT:[策略-价差]' instead of a clear statement like 'Get spread candlesticks'. The purpose is inferred from the tool name and schema, not stated. The description adds little value beyond labeling.

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 siblings like okx_get_spread_ticker or okx_get_spread_books. The only note is a prerequisite to call agent_catalog, but no comparison or selection criteria.

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