okx_stop_signal_bot

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

The description marks the tool as a write operation ('[L:WRITE]') but provides no detail on the effects of stopping a signal bot (e.g., whether positions are closed, orders cancelled). With no annotations, this lack of behavioral context is a significant gap.

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 concise, consisting of a single line that front-loads the category and operation type. While it lacks thoroughness, it avoids unnecessary verbosity.

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?

With one parameter, no output schema, and no annotations, the description does not cover expected responses, error conditions, or the full effect of the operation. The prerequisite hint is helpful but insufficient for complete understanding.

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 already describes the single parameter 'algoId' with a Chinese description. The tool description adds no further parameter details but hints that the ID can be obtained from agent_catalog. Given 100% schema coverage, this baseline score 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 only provides a category label and a prerequisite instruction. It does not explicitly state that the tool stops a signal bot; the purpose is only implied by the tool name. This vagueness hampers quick understanding.

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 mentions '请先调用 agent_catalog' as a prerequisite, giving a hint on when to use this tool. However, it does not differentiate from alternative tools or specify when not to use it. The guidance is minimal but present.

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