okx_get_ticker

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

No annotations are provided, so the description must carry full behavioral disclosure. It discloses that the tool returns current price, 24h change, and volume, which is the core behavior, but it does not mention additional context such as rate limits, error handling, or whether it supports both spot and swap despite the schema indicating instType. This is adequate but not rich.

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 front-loads the key outputs (current price, 24h change, volume) and provides instrument examples. There is no filler or redundancy, making it highly efficient.

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 simple getter tool with only two parameters and no output schema, the description is reasonably complete. It states the purpose, the data returned, and gives instrument examples. It does not enumerate all return fields, but the primary ones are covered, and the schema handles parameter details, so the description is sufficient for 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?

The input schema has 100% coverage with descriptions for both instType ('SWAP = perpetual futures, SPOT = spot') and instrument ('Trading pair, e.g. BTC-USDT, ETH-USDT, SOL-USDT'). The description adds example instruments (OKB-USDT) that are not in the schema, but this marginal addition does not exceed the baseline of 3 for high schema coverage.

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 retrieves current price, 24h change, and volume for an OKX instrument, which is a specific verb+resource combination with a clear scope. It does not explicitly differentiate from siblings like okx_get_candles or okx_get_market_data, but the focus on 'current' and specific data points makes its purpose distinct.

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 usage when a current market snapshot is needed, but provides no explicit guidance on when to use this tool over alternatives. There are no exclusions or references to sibling tools, leaving the selection decision partly to the agent's inference.

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