okx_stop_recurring_plan

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

The description indicates a write operation ('[L:WRITE]') but fails to disclose behavioral details such as whether the action is irreversible, what happens to associated orders, or authentication requirements. With no annotations, this is 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 cryptic and not well-structured. It uses tags and Chinese without clear English explanation, making it inefficient for quick comprehension.

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 tool with one parameter and no output schema, the description is incomplete. It does not explain the return value, side effects, or error scenarios. The prerequisite is mentioned but overall context is lacking.

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. The description adds the prerequisite hint about calling 'agent_catalog', implying where to obtain the 'algoId', which is a marginal improvement over the schema alone.

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 uses cryptic metadata like '[L:WRITE]' and 'CAT:[策略-网格]' but does not explicitly state that the tool stops a recurring plan. The tool name provides a hint, but the description is insufficient for an agent to quickly understand the action.

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, which is a prerequisite, but it does not specify when to use this tool versus alternatives like 'okx_create_recurring_plan' or 'okx_get_recurring_orders_pending'. No explicit context for selection.

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