okx_get_asset_valuation

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 hints at read-only via '[L:READ]' but does not disclose any behavioral traits such as authentication requirements, rate limits, or what happens if agent_catalog has not been called. The description is insufficient for understanding the tool's behavior.

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 lacks clarity and structure. While conciseness is valuable, it under-specifies the tool's purpose and usage, making it cryptic rather than efficient. Every sentence should earn its place; here, the instruction to call agent_catalog is not fully explained.

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 simple parameter and no output schema, the description should at least explain what the tool returns or how to interpret the output. It fails to do so. The dependency on agent_catalog is mentioned but not elaborated, leaving the agent uncertain about preconditions.

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 description coverage is 100% ('计价币种，如 USD、CNY。不填默认按所有币种'), so the baseline is 3. The description '请先调用 agent_catalog' does not add meaning to the parameter, and the parameter is adequately explained in the schema. No additional semantics added.

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:[账户]' and a Chinese instruction to call agent_catalog first, but does not explicitly state that the tool retrieves asset valuation. The name implies the purpose, but the description itself is vague and requires inference.

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 on when to use this tool versus siblings (e.g., okx_get_balance, okx_get_account_bills). The only instruction is to call agent_catalog first, which is a prerequisite, not a usage guideline. No alternatives or context provided.

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