hcm_atom_reset_checkpoint

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

The description adds the constraint 'Local store only,' which clarifies that the reset does not affect remote sources—a useful behavioral detail beyond the readOnlyHint=false annotation. However, it does not disclose potential side effects, such as whether clearing the checkpoint causes reprocessing of all entries or if it is irreversible. Given the annotation only marks it as a write operation, the description adds some value but leaves out important consequences.

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 extremely concise—two short sentences with no filler. The action and scope are front-loaded, and every word earns its place. This is an example of efficient, high-density documentation.

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 tool with one optional parameter and no output schema, the description covers the basic mechanics (clears a checkpoint, local-only, optional scope). However, it omits any guidance on when to use it or what happens to in-flight consumers, which might be critical for an agent deciding whether to invoke this destructive operation. Given the low complexity, a score of 3 seems fair—adequate but with a noticeable 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?

Schema description coverage is 0%, so the description must compensate. It does clarify that the 'collection' parameter is optional by saying '(or all)', implying that omitting it clears all checkpoints. However, it does not specify the expected format (e.g., name vs. ID) or how a single collection is identified. This is minimal but useful semantics.

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 action ('Clear'), the resource ('Atom CDC checkpoint'), and the scope ('for a collection (or all)'). This is a specific and unambiguous verb-resource pairing that distinguishes it from sibling tools like hcm_atom_get_checkpoint (which retrieves) and hcm_atom_poll/consume (which process entries).

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 guidance is provided on when to use this tool versus alternatives. It does not mention scenarios where resetting a checkpoint is appropriate, nor does it reference sibling tools like hcm_atom_get_checkpoint for comparison. The only contextual hint is 'Local store only,' which is behavioral rather than usage-oriented.

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