ck_checkpoint_create

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

Description adds moderate behavioral context beyond annotations: it indicates a mutating operation ('Create') and what is captured, but does not disclose side effects, authorization needs, or whether earlier checkpoints are affected. Annotations are minimal, so description carries burden.

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?

Single sentence, direct and informative with no redundant words. All information is front-loaded and essential.

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?

With 5 parameters (1 required, 1 enum) and an output schema, the description is too brief to fully guide usage. It lacks parameter details and usage scenarios, but is adequate for a simple create operation. The output schema likely documents return values, partially compensating.

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 has 80% description coverage (4 of 5 parameters described). The description adds no additional meaning to any parameters, relying on schema. Baseline 3 is appropriate as no further value is provided.

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?

Clear verb 'Create' and specific resource 'workspace checkpoint' with details of contents (git state, workspace context, metadata) and purpose (migration or rollback), distinguishing it from sibling tools like ck_checkpoint_restore.

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?

Description implies usage for creating checkpoints but provides no explicit guidance on when to use this tool versus alternatives such as ck_rollback or other snapshot tools, nor any conditions or prerequisites.

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