checkpoint

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

No annotations provided, but description discloses all key behaviors: saves to .agentpack/checkpoints, captures git state, updates status and next actions, seeds next load_context. Could mention permissions or reversibility, but still covers main behavioral traits.

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, action first, then usage guidance. No redundant words. Front-loaded with 'Save a durable progress checkpoint' – clear and efficient.

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?

Despite no output schema, the description covers what the tool does, where it stores, what it captures, and when to use. No missing information for this complexity level.

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%, so baseline 3. The description adds context by explaining that parameters replace previous values and that checkpoint captures git state automatically, which is not a parameter. This adds value beyond 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?

The description clearly states the tool saves a progress checkpoint with summary, git state, and updates status and next actions. It distinguishes itself from siblings like load_context by focusing on saving progress.

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?

Explicit guidance: call after meaningful progress, before ending session, before risky changes, and not after every small step. This provides clear when-to-use and when-not-to-use.

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