okx_get_account_config

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, permissions, rate limits, or whether the operation is truly read-only. The cryptic tag '[L:READ]' is not a clear behavioral statement. The agent has no insight into what this tool does beyond the name.

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 cryptic, using tags and Chinese without clear natural language. The prerequisite instruction is useful but the overall structure is not clear for an AI agent. It lacks explanatory text and is not well front-loaded with purpose.

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 and no annotations, the description is incomplete. It does not explain what the tool returns or what 'account config' means. The hint to call agent_catalog is vague. The agent cannot determine if this tool is useful without additional 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 no parameters, so schema coverage is 100%. The description adds no parameter information, which is acceptable given zero parameters. Baseline is 4 for this case, and the description does not contradict the schema.

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 uses cryptic tags like '[L:READ]' and 'CAT:[账户]' which suggest it is a read operation for account configuration, but it does not explicitly state what the tool does. The phrase '→ 请先调用 agent_catalog' is a prerequisite instruction, not a purpose statement. The tool name 'okx_get_account_config' is more informative than the description.

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 provides a prerequisite ('call agent_catalog first') but does not explain when to use this tool versus other account-related sibling tools like okx_get_balance or okx_get_account_rate_limit. No exclusions or context for selection are given.

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