Restore an agent's saved checkpoint to recover its previous state and resume operations after an interruption. This re-establishes the agent's memory and context.
Restore the latest checkpoint for an agent.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | The agent whose checkpoint to restore. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'restore,' which implies a state-changing operation, yet annotations declare readOnlyHint=true and destructiveHint=false. This is an annotation contradiction: nothing reconciles the side effects of restoring a checkpoint with the claim that the tool is read-only.
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. It states the operation clearly and compactly.
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 one-parameter tool with a complete schema, the minimum callable information is present. However, the definition omits usage guidance and leaves the read-only/restore contradiction unresolved, so an agent cannot fully judge the tool's effect or when to invoke it.
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 description coverage is 100%, so the schema already documents agent_id fully. The description's 'for an agent' adds no new meaning beyond the schema, so the baseline of 3 applies.
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 names a specific action ('restore'), a precise object ('the latest checkpoint'), and the target ('for an agent'), making it immediately distinguishable from sibling checkpoint_save and the memory_* tools. No ambiguity about what the tool does.
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 gives no guidance on when to choose this tool over checkpoint_save or the memory tools, and it does not state prerequisites or exclusions. The intended context is only implicit in the verb 'restore'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.