okx_get_flexible_loan_collateral

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

With no annotations provided, the description carries the full burden. It only indicates read-only via '[L:READ]' but lacks any disclosure about side effects, authentication requirements, rate limits, or the format of returned data. The description is insufficient for an agent to anticipate tool 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 (two segments), which is concise, but it sacrifices clarity. The directive to call agent_catalog is front-loaded, but the overall lack of substance makes it less useful. It is not verbose, but it is also not adequately informative.

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 tool has no parameters, no output schema, and no annotations, the description should explain what data is returned and its relation to sibling tools. Instead, it only directs to agent_catalog, leaving the agent without sufficient context to use the tool correctly. The complexity is low, but the description is incomplete.

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 zero parameters and 100% description coverage, so the baseline is 3. The description adds no additional semantic information beyond the schema. It does not explain what the tool fetches or how to interpret the lack of parameters.

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 states '[L:READ]' and 'CAT:[金融]' which hint at a read operation on financial data, but it does not clearly define what 'flexible loan collateral' means or what the tool returns. The phrase '→ 请先调用 agent_catalog' suggests it is not a standalone tool, muddying its purpose.

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 provides minimal guidance: '请先调用 agent_catalog'. It does not explain when to use this tool versus alternatives like okx_get_flexible_loan_info or okx_adjust_collateral, nor does it specify any context for usage.

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