Restore a Durable Checkpoint

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

Annotations are all false or unhelpful, so the description carries the full burden, but it only mentions abstract checks and never explains what loading does to current state, whether it overwrites the active session, or what the 'checks pass' failure mode looks like. The title says 'Restore,' suggesting mutation, but the description never clarifies the behavioral impact.

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, and the core action 'Load a checkpoint' is front-loaded. The trailing list of validation checks is compact, though somewhat jargon-heavy.

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?

Despite having an output schema and fully described parameters, the description leaves the operation's semantics vague: what does 'load' mean for the current session, and what does the caller need to know about preconditions or side effects? The undefined check list is not actionable guidance, so the description is inadequate for a state-affecting restore tool.

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%, and both parameters have useful descriptions, so the baseline is 3. The description's mention of 'state hash, expiry, ledger integrity, and lineage' hints at what the checkpoint_id encodes but does not add concrete meaning beyond the schema.

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 names a clear verb and resource: 'Load a checkpoint' with the title 'Restore a Durable Checkpoint', making the tool's core purpose evident. It does not explicitly differentiate itself from siblings like retrieve_context or checkpoint_save, but the name and title largely carry that distinction.

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 description provides a clear precondition: load only after 'session, scope, state hash, expiry, ledger integrity, and lineage checks pass.' This tells an agent when it is appropriate to invoke the tool. It does not name alternatives or exclusions, which keeps it just below the top of the scale.

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