okx_get_subaccount_trading_balance

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

The [L:READ] tag hints at read-only behavior, but no other behavioral traits (e.g., required permissions, rate limits, or side effects) are disclosed. With no annotations, the description should provide more depth.

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 the structure is functional. It could be better organized to front-load the core purpose instead of relying on tags.

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 lack of output schema and the tool's purpose (retrieving trading balance), the description should explain what data is returned or why agent_catalog is needed. It is incomplete for effective usage.

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?

Schema coverage is 100% and the parameter 'subAcct' is described in the schema. The description adds no additional meaning beyond the schema, meeting the baseline of 3.

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 a vague 'L:READ' and category tag, but does not explicitly state that the tool retrieves the trading balance for a subaccount. The name implies this, but the description fails to clarify.

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?

Only a prerequisite note ('请先调用 agent_catalog') is provided, with no guidance on when to use this tool vs. sibling tools like okx_get_subaccount_balance, or any context about scenarios.

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