openclaw_sessions_compaction_restore

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

Explicitly warns that the operation is destructive, overwrites the current session state, and that state is lost unless branched first. This goes beyond the missing annotations.

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?

Three concise sentences, each adding value: purpose, technical reference, and a critical warning. No fluff.

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 simple restore operation with a well-described schema, the description covers the essential behavioral aspects and prerequisite conditions adequately.

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 description does not add any parameter semantics beyond the input schema, which already has 100% coverage with clear descriptions. 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 clearly states the action ('Restore a session to a previous compaction snapshot') and the resource, distinguishing it from sibling tools like compaction_list and compaction_branch.

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?

Provides clear context: it is destructive and advises branching first to avoid losing current state. However, it does not explicitly state when to use this versus alternatives like creating a new session.

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