okx_get_account_rate_limit

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

No annotations are provided, and the description only indicates it is a read operation. It does not disclose side effects, authorization requirements, rate limits, or any behavioral traits beyond the implicit read-only nature.

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 brief (one line) but lacks clarity and structure. It is not front-loaded with the primary purpose and includes a confusing prerequisite. It sacrifices completeness 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 absence of annotations and output schema, and the minimal description, the tool definition is incomplete. It fails to explain what the tool returns, its context, or how it fits with sibling tools, leaving the agent without adequate information to use it correctly.

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 zero parameters, so schema description coverage is 100%. The description adds no parameter information, but since there are no parameters, it does not need to. 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 includes '[L:READ]' indicating it's a read operation and 'CAT:[交易]' for trading category, but it does not state what resource or function is being accessed (e.g., account rate limits). It redirects to 'agent_catalog' without explaining the tool's core purpose.

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 only mentions a prerequisite ('请先调用 agent_catalog'), but does not provide guidance on when to use this tool versus its many siblings (e.g., okx_get_ticker, okx_get_balance). No alternatives or exclusions are mentioned.

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