Save Active Session

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

With no annotations provided, the description carries the behavioral burden. It does state the core behavior: a unified checkpoint is saved so another harness can retrieve it via locate_and_load_session. However, it does not disclose side effects such as overwriting existing checkpoints, persistence details, or any permissions needed.

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 two sentences with no filler. The primary action is front-loaded, and the second sentence provides the exact invocation context. Every phrase 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?

For a checkpoint-saving tool, the description covers what it does, why it is used, and when to call it. The presence of an output schema covers return-value expectations, and the schema covers parameter details. It could be slightly more complete with caveats about repeated saves or overwrite behavior, but it is sufficiently complete for correct invocation.

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?

Input schema coverage is 100%, so the schema already documents all six parameters clearly. The description itself adds no parameter-level detail, which matches the baseline of 3 when the 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 opens with a specific verb and resource: 'Save a checkpoint of the current session (unified checkpoint)'. It also names the complementary sibling tool locate_and_load_session, making the tool's role in the workflow clear and distinguishing it from retrieval-oriented siblings.

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 gives explicit timing guidance: 'Call it before stopping (rate limit reached, end of session).' This tells the agent when to invoke the tool, though it does not explicitly discuss when not to use it or compare it against list_sessions or refresh_index.

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