okx_get_funding_rate_history

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

No annotations are provided, so the description must disclose behaviors. The label '[L:READ]' hints at read-only, but it is not a standard annotation and is ambiguous. The description does not mention pagination, rate limits, data periods, or any other behavioral traits. This is severely lacking.

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 at the cost of omitting essential information. It under-specifies rather than being concise. There is no wasted text, but the trade-off is poor completeness.

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 4 parameters, no output schema, and no annotations, the description is critically incomplete. It fails to explain the return format, pagination details, or any context about funding rate history. The note to call agent_catalog suggests additional context is needed, which is a sign of missing information.

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 100% of parameters with descriptions. The tool description adds no extra meaning for parameters beyond what the schema provides. Baseline 3 is appropriate as the schema does the work.

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 just a label '[L:READ]' and category 'CAT:[公共]' with a note to call agent_catalog. It does not explicitly state that the tool retrieves historical funding rates for OKX instruments. The purpose can be inferred from the name, but the description itself is vague and lacks a clear verb+resource statement.

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 alternatives. The sibling 'okx_get_funding_rate' likely returns the current funding rate, but this distinction is not mentioned. The note to call agent_catalog first is a prerequisite, not usage differentiation.

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