Remove an unwanted strategy by its ID to free up reasoning space and reset the decision tree.
Clear a specific strategy by ID
| Name | Required | Description | Default |
|---|---|---|---|
| strategyId | Yes | The ID of the strategy to clear |
Changes observed during successful MCP inspections.
v1.6.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but 'Clear' is ambiguous: it does not disclose whether the strategy is deleted, reset, or emptied, what side effects occur, whether the operation is reversible, or whether permission is required. This is insufficient for a mutation tool.
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?
A single, focused sentence with no filler. All words contribute to the meaning, and the key target (specific strategy by ID) is front-loaded.
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 tool is simple, but the lack of behavioral detail and usage context leaves an agent unable to fully predict what will happen. With no output schema and no annotation, the description should explain the effect and result of clearing a strategy.
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 the single parameter is already well documented. The description adds no new meaning beyond 'by ID', matching the baseline of 3.
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?
Description is 'Clear a specific strategy by ID' — a specific verb, resource, and targeting mechanism. It clearly distinguishes clear_strategy from siblings like clear_tree and clear_everything by naming the strategy resource and ID-based targeting.
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 about when to use this tool versus alternatives like delete_session_trees, clear_tree, clear_everything, or get_strategy. The description implies the action but provides no context for selection or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.