okx_get_savings_lending_rate

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

No annotations are provided. The description only contains a non-standard '[L:READ]' hint, which vaguely suggests read-only behavior but lacks clarity. No disclosure of side effects, idempotency, or other behavioral traits.

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 lines), which is concise but at the expense of content. It includes a prerequisite instruction that may be better placed elsewhere. It is not front-loaded with the core purpose.

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 output schema and no annotations, the description is severely lacking. It does not explain what the output looks like, how pagination works, or any context about savings lending rates. The agent cannot confidently use this tool based on the description alone.

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% description coverage for the single parameter 'ccy', which is well documented. The tool description adds no additional meaning beyond the schema. 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 '[L:READ] CAT:[统计]' is vague and does not explicitly state that the tool retrieves the lending rate for savings. It implies a read operation and statistics category but lacks a clear verb and resource.

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', but does not provide any guidance on when to use this tool versus its many siblings (e.g., okx_get_savings_balance, okx_get_lending_rate_history). No when-to-use or when-not-to-use advice.

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