okx_get_currencies

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation ('READ') but fails to describe what the tool actually does, whether it has side effects, or any limitations. The instruction to call agent_catalog adds confusion rather than clarity.

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 meaningful content. Conciseness is only valuable when information is effectively conveyed; here, it sacrifices clarity for brevity.

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 simplicity of the tool (one optional parameter, no output schema), the description still fails to explain the purpose or expected return values. The instruction to call agent_catalog is cryptic and does not compensate for missing context.

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% description coverage, with the 'ccy' parameter already documented. The description adds no additional value beyond what the schema already provides, so a baseline score of 5 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 only provides a read hint and category tag ('[L:READ] CAT:[资金]'), without explicitly stating the tool's purpose. The name 'okx_get_currencies' suggests retrieving currencies, but the description does not confirm this or specify what information is returned.

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 contains an instruction to call agent_catalog first, but does not explain when to use this tool versus alternatives like okx_get_ticker or okx_get_instruments. No guidance on context or prerequisites is provided.

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