stopStrategy

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

Since no annotations are provided, the description fully covers behavioral traits. It details the sequence: strategy status becomes 'Terminated,' all pending orders canceled immediately, partially filled orders canceled, filled orders unchanged, and execution stats preserved. It also mentions that terminateType is set to 'UserStop' and that all child orders are canceled. A rate limit of 10 requests/second is disclosed.

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 well-structured with clear sections: introduction, when-to-use, step-by-step outcome, important notes, and agent hint. Every sentence adds value, and the length is appropriate for the detail needed.

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 no annotations and no output schema, the description thoroughly explains the effect, side effects (orders canceled, stats preserved), and practical usage (agent hint, common requests). It covers all necessary context for an agent to use it correctly.

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 has 0% coverage, so the description compensates. It states that the required parameter is strategyId and provides guidance: 'Requires strategyId - if not provided, query strategy list first.' This adds meaning beyond the schema's bare type declaration.

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 clearly states 'Terminates an active strategy and cancels all associated pending orders.' It specifies the action and the resource, and distinguishes stopStrategy from sibling tools like closeComboBot or createTwapStrategy by focusing on strategies and their termination.

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 'When to use' section lists explicit scenarios such as stopping before completion, reacting to market changes, or emergency risk management. It also notes that stopped strategies cannot be restarted and that to continue one must create a new strategy, providing good usage context. However, it does not explicitly contrast with alternatives like closeGridBot or closeDCABot.

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