snapshot_session

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

With no annotations, description accurately states it saves a snapshot and returns an id. It discloses the snapshot content (transcript + carry-forward block) but does not mention side effects, permissions, or whether it modifies existing data.

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?

Three sentences: purpose, use cases, return value and input source. Each sentence is necessary and front-loaded, no wasted words.

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 no output schema, description explains return value (snapshot id). Explains what snapshot contains and how to get threadId. Fits well with sibling tools for listing/loading snapshots.

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 covers both parameters (100% coverage), so baseline is 3. Description adds value by specifying that threadId should come from search_threads, providing extra usage guidance beyond the schema.

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 specifies exactly what the tool does: save a resumable snapshot of a thread including transcript and carry-forward block. It clearly distinguishes from sibling tools like list_snapshots and load_snapshot by focusing on creation.

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 when-to-use scenarios (checkpoint before context compaction, handoff to another agent/tool) and tells users to pass a threadId from search_threads. Lacks when-not-to-use but context is clear.

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