okx_get_ticker

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

The description includes a '[L:READ]' tag indicating a read-only operation, but provides no other behavioral details such as rate limits, required permissions, or data freshness. Since no annotations are present, the description should carry more weight but fails to do so.

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 substance; it is under-specified rather than concise. Every sentence should earn its place, but the existing text does not provide value to the agent.

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 lack of output schema and the large number of sibling tools, the description should clarify return values and differentiate from similar tools. It fails to do so, making the tool insufficiently described for effective selection and invocation.

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 parameter 'instId' is well-described in the schema (including examples and batch query support). The description adds no additional meaning beyond the schema, 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 does not clarify what the tool does; it only contains a category tag '行情' and a note to call agent_catalog first, which is misleading. The tool's name implies getting a ticker, but the description fails to explicitly state that.

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 siblings like okx_get_tickers. The instruction to call agent_catalog first is not useful usage guidance and adds confusion.

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