okx_quick_market

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

Since no annotations are provided, the description carries full burden. It explicitly states 'READ' and '只读查询' (read-only query), and notes return size (~2KB, 5-depth, not full orderbook). This is adequate for a read-only 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?

Description uses structured headers and lists, making it easy to scan. It is slightly verbose but every section adds value. Could be more concise but still good.

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 read-only market snapshot with one parameter, the description covers functionality, usage scenario, auth, risk, return size, and related tools. It is fully complete for agent understanding.

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 coverage is 100% with a clear description for instId. The description repeats the parameter info but adds no new semantics beyond the schema. Baseline 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 function: returning a structured summary of market data (ticker, 5-level depth, funding rate, product specs) for a given product. It distinguishes from siblings by combining multiple data points into one call.

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 concrete use case ('now BTC what's the situation') and a tool chain: this tool for quick overview, then okx_get_candles for deeper K-line, okx_get_orderbook for full depth, okx_place_order for trading. It also mentions the tool is read-only and public.

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