okx_get_trade_fee

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

No annotations and no behavioral disclosure. The description does not mention whether this tool is read-only, what actions it performs, or any side effects. The prerequisite hint is unclear and 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 very short but contains non-English text and unclear symbols. It does not effectively communicate the tool's purpose, making it not genuinely concise.

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 lacks essential information about return values, behavior, and context. Given no output schema, the description must explain what the tool returns, but it fails to do so. The prerequisite is ambiguous.

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 coverage is 100%, so each parameter has a description. The description adds no additional meaning beyond the schema. 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 does not state what the tool does. It contains a cryptic note '[L:READ] CAT:[账户]' and a prerequisite to call agent_catalog, but does not explain the purpose of 'okx_get_trade_fee'. The tool name suggests retrieving trade fees, but the description fails to convey that.

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?

No guidance on when to use this tool versus alternatives. The note '请先调用 agent_catalog' implies a prerequisite but is not helpful for usage decision. No explicit context or exclusions provided.

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