okx_get_funding_balance

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

With no annotations provided, the description must disclose behavioral traits. It only marks the tool as read ([L:READ]) but does not mention authentication requirements, rate limits, or what type of data is returned. The prerequisite hint is insufficient.

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 short, but it is not effectively concise because it lacks critical information. It is more cryptic than clear, and the prerequisite instruction adds ambiguity rather than clarity.

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?

The description is severely incomplete. Given the tool has one optional parameter and no output schema, the description should explain what a funding balance is, how it differs from other balance endpoints, and what the response contains. None of this is provided.

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 schema covers 100% of the parameter description, and the tool description adds no extra meaning beyond what the schema already provides. The baseline score of 3 is appropriate.

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 fails to explicitly state that the tool retrieves the funding balance for OKX. Instead, it only provides a read indicator and a prerequisite instruction. The name implies the purpose, but the description itself is vague and does not clarify what the tool does.

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 only instructs to call agent_catalog first, without explaining when to use this tool versus alternatives like okx_get_balance or okx_get_margin_balance. No differentiation from sibling tools is provided.

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