okx_get_sprd_history_candles

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

No annotations exist, so the description must carry the burden. It only hints at read-only via '[L:READ]', but provides no details on rate limits, error handling, or response format. Behavioral expectations remain unclear.

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 extremely short but underspecified. It fails to convey the tool's function in a helpful way, prioritizing brevity over clarity. Not an example of effective conciseness.

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?

For a tool with 5 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain what the tool returns, how pagination works, or how to interpret results. Complete inadequacy.

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?

All 5 parameters are documented in the input schema with descriptions, achieving 100% coverage. The description adds no extra meaning, but the schema already explains each parameter. 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?

The description is cryptic: '[L:READ] CAT:[行情] | → 请先调用 agent_catalog'. It does not clearly state that this tool retrieves historical candles for a spread contract. The purpose is only vaguely inferable from the tool name and parameter schema.

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 instructs to call 'agent_catalog' first, but gives no context on when to use this tool versus siblings like 'okx_get_spread_candles' or 'okx_get_candles'. No comparison or selection criteria provided.

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