okx_get_interest_limits

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

No annotations are provided, so the description carries the full burden. It only contains metadata tags and a prerequisite hint, with no disclosure of side effects, authentication needs, rate limits, or any behavioral traits. This is completely inadequate.

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 very short, but conciseness should not sacrifice clarity. It lacks substantive information and reads as a fragment. Every part is cryptic (tags, Chinese text), and it does not earn its place in helping an agent understand the tool.

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 no output schema, no annotations, and a cryptic description, the tool is completely unexplained. An agent cannot determine what interest limits are, how they are returned, or any contextual details. This is insufficient for a tool with zero parameters.

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 tool has zero parameters and 100% schema coverage, so the baseline is 4. However, the description adds no meaning beyond the empty schema. It fails to explain what the tool returns or its purpose, which the schema cannot convey. Thus, the description provides minimal value.

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 contains a tag L:READ and CAT:[账户] hinting at a read operation on account data, but it does not explicitly state what the tool does. The name 'okx_get_interest_limits' suggests retrieving interest limits, but the description lacks a clear verb and resource explanation, making it vague.

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 says '→ 请先调用 agent_catalog' (call agent_catalog first), providing a prerequisite but no context on when to use this tool over alternatives or when not to use it. Sibling tools include many OKX account tools, but 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.