replay_checkpoint

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds that the checkpoint is forced immediately and scoped to the current session, but it does not disclose side effects, persistence behavior, or failure modes. No contradiction with annotations.

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?

One concise, front-loaded sentence with no redundant phrasing. Every word earns its place, and the most important action and scope appear immediately.

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?

The tool is low in complexity with one optional parameter, but the description omits practical context such as whether an active session is required, what happens if no session exists, and what the agent can expect after calling it. Since there is no output schema, a bit more guidance would improve completeness.

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?

The input schema already documents the single optional 'note' parameter completely, so the description adds little semantic value beyond restating that the note is optional. With 100% schema coverage, the baseline of 3 is appropriate.

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 uses a clear directive verb ('Force') plus an explicit resource ('checkpoint of the current session') and mentions the optional note. This distinguishes it cleanly from sibling tools like replay_resume or replay_export, which perform different operations.

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?

No explicit guidance on when to use this tool versus alternatives. It does not state prerequisites such as requiring an active session, nor does it say when checkpointing is preferable to replay_status, replay_export, or replay_diff. The only contextual clue is 'current session'.

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