okx_get_subaccount_bills

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

No annotations exist, so the description must disclose behavioral traits. It only provides a '[L:READ]' tag (likely read-only) and a category, but no details on authentication, rate limits, or consequences of not calling agent_catalog first.

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 and front-loaded, but it uses opaque tags that may confuse an AI agent. It is not particularly helpful despite being concise.

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?

With no output schema and 4 parameters (1 required), the description provides no information about return values, pagination, or behavior. The sole directive to call agent_catalog first is insufficient for an agent to use the tool 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 100% coverage with Chinese descriptions for all 4 parameters. The tool description adds no information beyond what the schema already provides, so baseline score of 3 applies.

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 cryptic tag '[L:READ]' and tells to call agent_catalog first, but does not explicitly state the tool's action. The purpose is mostly inferred from the name 'get_subaccount_bills', making the description a tautology.

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 only usage guidance is '先调用 agent_catalog' (call agent_catalog first), which is a prerequisite. There is no mention of when to use this tool versus alternative sibling tools like okx_get_subaccount_balance or okx_get_subaccount_list.

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