okx_get_tickers

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

No annotations are provided, and the description only includes a generic READ label and category. It does not disclose rate limits, authentication requirements, data scope, or any behavioral traits. The tool's behavior remains opaque.

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 substantive content. It front-loads 'READ' and 'CAT', but these are not official annotations. The instruction to call agent_catalog is cryptic. Conciseness is achieved at the cost of clarity.

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 absence of an output schema, the description should explain what tickers are returned (e.g., latest prices, volumes). It does not. The tool is part of a large sibling group, yet no context is provided about its specific role or relation to other tools.

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% and the single parameter 'instType' already has a clear description ('产品类型') and enum. The description adds no additional semantic meaning beyond what the schema provides, so 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 labels the tool as READ and market data (CAT:[行情]), but does not explicitly state that it retrieves multiple tickers for a given instrument type. The instruction '请先调用 agent_catalog' is vague and does not clarify the tool's function. Sibling 'okx_get_ticker' suggests singular vs plural, but the description fails to differentiate.

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_ticker' or other market data tools. The only hint is to call 'agent_catalog' first, but there is no explanation of selection criteria or context.

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