okx_get_market_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the scope (perpetual contracts) but does not state whether this is read-only, what the response format looks like, or any limitations or prerequisites. For a market data tool, more detail would be expected.

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 a single concise sentence that names the action and all key data points without any wasted words. It is well-structured and front-loaded.

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?

With one optional parameter, no output schema, and no annotations, the description is reasonably complete but does not explain whether all three data types are returned in a single response, nor does it mention the optionality/default of the instrument parameter. It falls short of full completeness but is adequate for a simple market data fetch.

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 already provides 100% coverage of the one parameter with a clear description and default value. The tool description adds no additional parameter semantics beyond what the schema specifies, so the 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 clearly states the tool gets derivatives market data and specifies the exact data types: Open Interest, Long/Short Ratio, and Funding Rate, and scopes it to perpetual contracts. This distinguishes it from sibling tools like okx_get_ticker or okx_get_candles.

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 implies when to use the tool (when you need derivatives market data) but does not explicitly state when not to use it or provide alternatives. There is no mention of comparing with okx_get_ticker for spot data or other tools, so guidance is minimal.

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