okx_get_account_bills_archive

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

No annotations are provided, and the description only includes a '[L:READ]' tag indicating read-only, but does not disclose any behavioral traits such as authentication requirements, rate limits, data freshness, or potential side effects. The description carries full burden but adds minimal value.

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 extremely concise, consisting of a single line with tags and a prerequisite instruction. While it is short, it is not verbose, and the structure is clear. However, it could be more informative without increasing length significantly.

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 parameters, the description fails to explain what the tool returns, how it relates to similar tools like 'okx_get_account_bills', or any contextual details about data scope (e.g., time range, filtering). The description is insufficient for an agent to confidently use the tool.

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 tool has no parameters (0 parameters, schema coverage 100% trivially). The description does not need to add parameter information, and the lack of parameters is clear from the schema. The description is adequate in this dimension.

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 indicates a read operation for 'account bills archive' but does not explain what 'bills archive' means or how it differs from the sibling tool 'okx_get_account_bills'. The purpose is vague and lacks specificity.

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 instructs to call 'agent_catalog' first, suggesting a prerequisite, but does not provide context on when to use this tool versus alternatives like 'okx_get_account_bills' or others in the account category. No exclusions or clear usage guidance.

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