okx_search_instruments

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

The description includes a read hint ([L:READ]) and public category, but without annotations, the burden is on the description to disclose behavioral traits. No additional behaviors (rate limits, pagination, response format) are mentioned. It is insufficient for an agent to understand the tool's impact.

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 (one line) but it is not structured as a clear purpose statement. It reads more like an internal note than a description for an AI agent. While brevity is valued, the content is insufficient and lacks key information.

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 tool has 2 parameters and no output schema, the description should explain what results to expect and how the search works. The current description does not differentiate this tool from many similar market data tools, leaving the agent without enough context for correct selection.

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 covers 100% of parameters with descriptions, so the baseline is 3. The tool description adds no extra meaning beyond the schema, so it remains at baseline.

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 only mentions it's a read operation and public, but does not explicitly state that the tool searches for instruments by keyword and instrument type. The tool name suggests the purpose, but the description itself is vague and does not clarify the action.

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 instructs to call agent_catalog first, which is a usage hint, but it does not provide guidance on when to use this tool versus alternatives like okx_get_ticker or okx_get_instruments. The context signals show many sibling tools for market data, and no differentiation is provided.

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