Manage checkpoint

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description details exactly what a checkpoint captures, what restore does (reapplies parameters, recreates deleted nodes, prunes created nodes), and frames it as an undo point. This is substantial behavioral disclosure that helps the agent understand destructive consequences.

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 four sentences, each earning its place: the action summary, the content of a checkpoint, the restore behavior, and the comparison with manage_presets. It is front-loaded with the core purpose and contains no filler.

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 multi-action tool, the description covers the purpose, content, restore semantics, and alternative, but it does not mention the return value or output format for the list action, which could matter for an agent choosing to use it. Still, with a rich schema and annotations, it is largely complete enough.

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%, so the baseline is 3. The description adds meaning by explaining how restore behavior maps to the prune_created and recreate_deleted parameters, and by clarifying that comp_path represents a full sub-network. This goes beyond the schema's field-level descriptions.

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 opens with a specific verb list ('Store / restore / list / delete a full snapshot of a sub-network') and clearly identifies the resource (sub-network snapshot). It distinguishes itself from manage_presets by contrasting whole-network capture with custom-parameter looks, making the tool's purpose unambiguous.

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 states when to use the tool ('before risky live edits', 'for safe experimentation') and explicitly names the alternative (manage_presets), explaining that this tool captures the entire network rather than just parameter looks. This gives the agent clear decision criteria.

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