okx_get_fills_history

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

No annotations are present, so the description must compensate. The '[L:READ]' tag indicates a read operation, which is helpful, but there is no disclosure of data freshness, pagination behavior, permissions, or any side effects. The description is insufficient for a tool with zero annotation coverage.

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 under-informative. It fails to deliver necessary details, making it incomplete rather than concise. Every sentence should earn its place; this one does not.

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's 3 parameters, no output schema, and large sibling set, the description is severely incomplete. It lacks any detail about return format, usage context, or tie-in to the broader API. The instruction to call 'agent_catalog' is cryptic and does not substitute for proper documentation.

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 description coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema; it merely contains a category tag and a prerequisite note. The parameter descriptions in the schema are adequate on their own.

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 vague. The name 'get_fills_history' and the category tag '[交易]' hint at retrieving historical trade fills, but the description fails to explicitly state the action and resource. It only says '→ 请先调用 agent_catalog' without defining the tool's primary 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 on when to use this tool versus siblings like 'okx_get_fills' or other fill-related tools. The prerequisite to call 'agent_catalog' is mentioned but not explained, and no alternatives or exclusions are provided.

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