checkpoint_session

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

No annotations are provided, so the description must bear full burden. It states the tool stores a compact checkpoint, but lacks details on side effects (e.g., whether it overwrites previous checkpoints, retention policy, authorization needs). With 10 parameters, the description does not expand on behavioral nuances beyond the compact nature.

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 consists of two tightly written sentences: the first states purpose, the second provides usage context. No extraneous words, and critical information is front-loaded. Every sentence earns its place.

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, the description does not explain return values, but this is acceptable for a write operation. It covers purpose and usage context but omits details like idempotency, session lifecycle, or integration with resume_context. Moderate completeness for a tool with 10 parameters and no annotations.

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 description coverage is 100%, so baseline is 3. The description adds minimal meaning beyond the schema, only mentioning 'compact'. It does not elaborate on parameter relationships, defaults, or formatting, leaving the schema to carry the semantic load.

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 'Store a compact checkpoint of the current work state', combining a specific verb (Store) with a resource (checkpoint of current work state). It distinguishes from sibling tools by noting it avoids polluting durable memory, contrasting with store_memory and other persistent storage tools.

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 guides use 'when a task spans windows or terminals and you need the next session to recover decisions, open loops, and next actions without polluting durable memory.' This provides clear context, though it does not explicitly mention when not to use it or compare to alternatives like store_memory or distill_session.

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