Manage checkpoint

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

The description discloses destructive behavior (restore prunes/recreates nodes) beyond annotations (destructiveHint=true), adding specific context about what happens during restore. No contradictions with 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?

Two sentences plus a comparison, no fluff. Front-loaded with purpose and usage context. Every sentence adds value.

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?

Given 5 parameters all described in schema, no output schema needed, and annotations providing safety cues, the description completes the picture with behavioral details and usage context.

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 100% with all parameters having descriptions. The description adds minimal extra meaning beyond the schema (e.g., action enum values). Baseline 3 is appropriate since schema does the heavy lifting.

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 tool's function (store/restore/list/delete checkpoints, an 'undo point' for sub-networks) and distinguishes it from manage_presets by emphasizing the scope difference: full snapshot vs. custom-parameter looks.

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 explicitly recommends using this tool 'before risky live edits' and contrasts it with an alternative (manage_presets), providing clear when-to-use and when-not-to-use guidance.

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