okx_get_spread_fills

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

The description only indicates it is a read operation via '[L:READ]' but provides no details about authentication, rate limits, or what happens when called. With no annotations, the description fails to disclose behavioral traits beyond the basic read hint.

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 concise (one line) but is cryptic and uses obscure prefixes. It could be shorter if clearer, but as written it is not effectively informative.

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?

The description lacks information about return values, which is critical since there is no output schema. It also does not explain the data structure or how fills relate to spreads, leaving the agent underinformed.

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?

Input schema coverage is 100%, with descriptions for limit and sprdId. The tool description adds no additional meaning beyond the schema, so 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 is cryptic: '[L:READ] CAT:[策略-价差] | → 请先调用 agent_catalog'. It does not explicitly state that the tool retrieves fills for spread orders, relying on the name to imply the purpose. The instruction to call agent_catalog first adds confusion without clarifying the tool's core function.

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 siblings like okx_get_spread_orders or okx_get_spread_trades_fills. The only hint is to call agent_catalog first, which is a prerequisite, not a usage guideline.

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