memory_checkpoint

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It doesn't say whether a checkpoint overwrites prior state, whether it is append-only, what permissions or active mission state are required, or whether concurrent checkpoints conflict. "Persist" signals a write, but the mutation semantics are left undefined.

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?

A single front-loaded sentence with no filler, which is structurally clean. It is under-specified rather than bloated, but the brevity leaves the definition with too little content to be genuinely useful.

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 write tool with no annotations, no output schema, and 0% parameter coverage, the definition is materially incomplete. An agent cannot determine required state, overwrite behavior, or the meaning of its two required and two optional parameters from the description alone.

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% across four parameters, so the description needed to compensate and does not. It never explains what project_id, mission_id, status, or next_action should contain, what format status takes, or what next_action is for. The field names are largely self-descriptive, which prevents a 1, but the description adds no semantic value.

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 pairs a specific verb ("Persist") with a specific resource ("handoff checkpoint"), which is more than a restatement of the name. It also hints at the audience ("another harness/agent"), loosely distinguishing it from read-oriented siblings like mission_status. However, it doesn't explicitly contrast itself with siblings such as delegate or mission_status, so it falls short of a 5.

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?

There is no statement of when to create a checkpoint versus using mission_status or delegate, and no prerequisites or exclusions are given. The audience hint ("for another harness/agent") implies a handoff scenario but the agent must infer the trigger condition entirely.

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