okx_set_lending_rate

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

No annotations are provided, and the description lacks any behavioral transparency. It does not mention whether the operation is idempotent, reversible, requires authentication, or has any side effects beyond a write operation.

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 fails to provide necessary information. The instruction to call agent_catalog is important but poorly integrated. It could be more structured to convey purpose and usage succinctly.

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?

For a write tool with 2 parameters and no output schema or annotations, the description is completely inadequate. It does not explain what the tool does, return behavior, or any operational considerations. The prerequisite hint is insufficient.

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?

Schema description coverage is 100% with 'ccy' and 'rate' described as required fields. However, the description adds no additional meaning beyond the schema, such as formats, allowed values, or examples. Baseline 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 includes a tag '[L:WRITE]' suggesting a write operation and 'CAT:[金融]' indicating finance, but it does not explicitly state that this tool sets a lending rate. The instruction to call agent_catalog first does not clarify the tool's function. Sibling tools like okx_get_lending_rate_summary suggest a related domain, but the purpose is vague.

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 says '→ 请先调用 agent_catalog' (please call agent_catalog first). It does not provide any guidance on when to use this tool versus alternatives, nor does it explain prerequisites or exclusions.

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