clear_everything

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

No annotations are present, so the description must fully disclose behavior. It does indicate destructive bulk clearing, but it omits critical context: irreversibility, what 'all' is scoped to (session, workspace, or global), whether strategies are deleted or emptied, and whether confirmation is required.

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 a single, front-loaded sentence with no filler. Every word earns its place for a tool with no parameters, making it highly efficient.

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?

Even with no parameters and no output schema, a destructive bulk operation needs more context: the scope of 'all', reversibility, and what exactly gets cleared (tree structures, strategy configurations, associations). The description lacks these essential details, leaving an agent to guess at the operational impact.

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 tool has zero parameters, so the description carries no parameter documentation burden. The empty schema is trivially complete, and the baseline for zero-parameter tools is 4.

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 'Clear all trees and strategies' states a specific verb (clear) and a broad resource (all trees and strategies), making it distinguishable from sibling tools like clear_tree, clear_strategy, or delete_tree. The scope 'all' conveys a bulk operation, though the difference between clearing and deleting is not explained.

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 is provided on when to use this tool versus alternatives such as clear_tree, clear_strategy, or delete_session_trees. The description does not specify selection criteria, prerequisites, or situations where this bulk clear should be preferred.

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