okx_get_fills

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

No annotations are provided, and the description only contains '[L:READ]' which hints at read-only behavior but is not definitive. It does not disclose any other behavioral traits, such as whether it returns historical or current fills, or if it requires authentication.

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 (two fragments) but under-specified. It lacks crucial information about the tool's purpose and usage. Brevity is not beneficial when it omits core meaning.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is woefully inadequate. It does not explain what 'fills' are, how to interpret results, or any constraints like pagination. The user is left entirely reliant on the schema.

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?

The input schema covers all 3 parameters with descriptions, so the description adds no additional parameter semantics. Baseline score of 3 applies since the schema already provides adequate 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 '[L:READ] CAT:[交易]' which is vague and does not clearly state that the tool retrieves filled orders. The name implies it, but the description fails to articulate the function explicitly. It does not distinguish from sibling tools like okx_get_fills_history or okx_get_spread_fills.

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 provides a prerequisite ('请先调用 agent_catalog'), which gives some guidance on order of operations. However, it does not specify when to use this tool versus alternatives, nor does it explain typical use cases or what inputs are needed.

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