okx_get_account_position_risk

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only includes a vague '[L:READ]' tag but does not explain any behavioral traits, such as whether it reads account data, requires authentication, or has side effects.

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?

While the description is short, it is not concisely informative—it is cryptic and incomplete, containing a prerequisite instruction rather than a clear explanation of 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 the likely complexity of retrieving position risk and the absence of an output schema or annotations, the description is extremely incomplete. It fails to describe the return format, risk metrics, or any context needed for safe use.

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?

There are no parameters, and schema coverage is 100%. The description adds no meaning beyond the empty schema, but the baseline for zero parameters is 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 is cryptic: '[L:READ] CAT:[账户] | → 请先调用 agent_catalog'. It does not clearly state that the tool retrieves account position risk. Instead, it instructs the user to call another tool first, obscuring the tool's primary function.

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?

No guidance is provided on when to use this tool versus alternatives like okx_get_positions or okx_get_balance. The only instruction is to call agent_catalog first, which is a prerequisite, not a usage guideline.

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