checkpoint_context

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

With no annotations, the description carries the full burden. It discloses key behaviors: saving state, resetting health score, and returning 'health before/after and entries saved.' It also explains the rationale (prevent loss to compaction), adding context beyond the schema. It does not detail every edge case but is transparent enough for a tool of this simplicity.

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 three sentences with no wasted words. It front-loads the primary action and includes usage guidance and return information efficiently.

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 simple tool with no output schema and full schema parameter coverage, the description covers the essential aspects: what it does, when to use it, and what it returns. It could benefit from explicit exclusions or alternatives, but the context signals (sibling names) help fill that gap.

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 schema already provides 100% coverage of all three optional parameters with descriptions. The tool description adds no additional parameter-specific details beyond the schema, so 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 clearly states the tool's function: 'Save the current workflow state and reset health score.' It also differentiates by mentioning 'before context is lost to compaction,' which distinguishes it from generic save_context. However, it does not explicitly name sibling alternatives, so it falls short of a perfect score.

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 provides explicit usage guidance: 'Use when health is critical or before long operations.' This tells the agent when to invoke the tool, though it does not discuss when not to use it or mention alternative tools, which would make it more comprehensive.

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