okx_get_mark_price

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

With no annotations provided, the description should disclose behavior. The [L:READ] tag hints at a read operation, but does not explain side effects, required permissions, or response format. The description is insufficient for a public API tool.

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 lacks informativeness. It prioritizes conciseness at the expense of clarity, and does not effectively front-load the tool's purpose. More detail is needed for a 2-parameter tool.

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 complexity of the OKX API and many sibling tools, the description fails to complete the context. It does not explain that this tool retrieves mark prices, nor differentiate it from similar tools. The prerequisite instruction is useful but not sufficient.

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 has 100% coverage with descriptions for both parameters (instId and instType). The description adds no additional meaning beyond what the schema already provides, so a 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 uses cryptic tags ([L:READ], CAT:[公共]) and a prerequisite instruction, but does not explicitly state that the tool retrieves mark prices for given instrument types. The purpose is vaguely implied by the tool name, but the description adds no clarity.

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 alternatives like okx_get_mark_price_candles or okx_get_instruments. The only instruction 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.