checkpoint_get

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

There are no annotations, so the description carries the full burden. It does convey that this is a read operation and that omitting checkpointId returns the latest checkpoint, which is useful behavioral information. However, it does not disclose return format, error behavior for missing checkpoints, or any permission/authentication requirements.

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 a single sentence with no filler. The core action, resource, and key distinction are front-loaded and immediately actionable.

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 simple, the required parameter is present, and the main selection behavior is explained. There is no output schema, so a bit more detail on what the returned checkpoint contains would improve completeness, but it is not necessary for an agent to select and invoke the tool correctly.

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 description adds meaning beyond the schema by explaining that checkpointId is optional and that its absence means 'latest checkpoint.' It also ties workspaceRoot and taskId to the scoping of the read. The schema covers two parameter descriptions, but checkpointId itself has no description, so the tool description fills that gap.

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 a specific verb ('Read') and resource ('checkpoint'), and differentiates the two access modes: a specific checkpoint or the latest checkpoint. This makes it obvious how it differs from sibling checkpoint_create even without naming it.

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 usage context is implied: it is the tool to call when you need to retrieve a checkpoint for a workspace/task. It does not explicitly discuss when not to use it or compare with alternatives, but the sibling tools are not direct alternatives for this read operation.

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