restore_checkpoint

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

With no annotations, the description carries the full behavioral burden, and it discloses one genuinely non-obvious trait: restoration only affects nodes that still exist. However, it omits whether this is destructive, whether it overwrites current node state, whether it is reversible, and what happens to nodes added since the checkpoint; the coverage question is explicitly punted to create_checkpoint.

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?

Two tight sentences with the core action front-loaded and the caveat immediately after; nothing is repetitive. The trailing cross-reference sentence earns its place as the only pointer to coverage semantics.

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 mutation tool with no annotations, no output schema, and an entirely undocumented parameter, the description does not say what a restore returns, how failures (e.g. no surviving nodes) are surfaced, or where checkpointId comes from. It covers purpose and one caveat but leaves the operation's contract largely unstated.

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 0% and the single required parameter checkpointId is undocumented in both schema and description. The description never says where to obtain the id (presumably from create_checkpoint or list_checkpoints) or what format it takes, so it fails to compensate for the coverage gap.

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?

States a specific verb ('reapply') and resource ('snapshot captured by create_checkpoint'), making clear it is the inverse of create_checkpoint rather than a listing or creation tool. An agent can distinguish it from create_checkpoint and list_checkpoints from the text alone, though the phrasing 'reapply a snapshot' is slightly indirect about the mutation.

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?

Usage is only implied: the agent must infer that this is for reverting to a previously captured state. It points to create_checkpoint for coverage details, which is a useful routing hint, but there is no explicit when-to-use, when-not-to-use, or statement about prerequisites such as which checkpoints are restorable.

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