memory_checkpoint

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

With no annotations, the description carries the full burden and does well: it discloses side effects ('create/resolve persist state and audit entries'), a failure condition ('resolving a non-pending checkpoint fails'), and the downstream effect ('passing can unblock actions'). Auth/permission requirements are unstated, keeping it below a 5.

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?

Front-loads the key distinction (a managed gate, not a live check) and then enumerates operations compactly. It is dense with semicolon-separated clauses but each sentence carries information; no filler.

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 6-parameter, multi-operation tool with no output schema and no annotations, the description covers operations, side effects, failure modes, and return shape ('checkpoint and unblock count, or a checkpoint list'). It is nearly self-sufficient, though permissions/reversibility remain unspecified.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it maps which parameters belong to which operation and explains the gating semantics of linkedActionIds and status ('passing can unblock actions'). This goes beyond the schema's field-level descriptions.

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?

States a specific resource (a recorded external gate / checkpoint) and scopes it against the obvious confusion: it manages the gate 'rather than performing a CI, approval or deploy check itself.' This separates it from sibling sentinel tools. The verb 'manage' is slightly generic, but combined with the per-operation detail the purpose is unambiguous.

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?

Gives operation-specific guidance ('create' requires name, 'resolve' requires checkpointId and passed/failed, 'list' reads) and names an alternative routing rule ('use sentinels for event-driven conditions'). It lacks explicit when-not-to-use guidance beyond that single alternative, so it falls just short of a 5.

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