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

Explicitly mentions the destructive nature (replaces current graph) and the side effect of re-registering webhook/cron resources, going beyond the destructiveHint annotation and giving clear behavioral expectations.

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?

Conveys purpose, behavior, and a warning in two concise sentences without unnecessary detail, making it easy to parse and act upon.

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?

Covers the essential aspects: the action, the side effects, and the irreversibility. An output schema is present, so not describing return values is acceptable.

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 elaborate on workflow_id or checkpoint_id. Since the schema provides no parameter descriptions (0% coverage), the description fails to add meaning, though the parameter names are somewhat self-explanatory.

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?

Clearly states it restores a workflow to a saved checkpoint, replaces the current graph, and re-registers webhook/cron resources. This distinguishes it from sibling tools like create_checkpoint or list_checkpoints.

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 explicit guidance that the operation is irreversible and recommends creating a checkpoint first if the current state is needed. However, it does not explicitly compare with alternatives like open_workflow, so it lacks a full when-to-use vs. when-not-to-use breakdown.

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