Create Restart Snapshot

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

Description indicates it's a write operation ('save'), consistent with readOnlyHint=false. It details what is saved (state, events, todos, decisions), going beyond annotations. Does not mention potential side effects like overwriting, but annotations already show non-destructive.

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: first explains function, second gives usage advice. No redundant information; 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 9 parameters and presence of an output schema (not shown), the description sufficiently explains the tool's purpose and usage scenario. It covers key behavioral aspects, though does not describe return values (likely covered by output schema).

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 descriptions for all 9 parameters. Description groups parameters by function (e.g., state, events, todos, decisions) but adds limited new meaning beyond what schema provides.

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?

Description clearly states the tool saves active state, recent events, TODOs, and pending decisions. It distinguishes itself from sibling tools like restore_restart_snapshot and other memory tools by specifying it's for creating a snapshot for restart.

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?

Explicitly states when to use: 'before handoff or when context may be lost.' Does not specify when not to use or list alternatives, but the guidance is clear and context-specific.

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