rms_checkpoint_load

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It indicates a read-like operation ('load'), but does not explicitly state whether it has side effects, requires authentication, or any other behavioral traits beyond the implied reading of checkpoints.

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?

Two sentences with no wasted words. The first sentence delivers the core purpose, and the second provides immediate, actionable usage guidance. Front-loaded and efficient.

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?

Given the absence of output schema, the description provides a reasonable overview of what the tool returns ('full body and bounded previews'). It also relates to its sibling tools by specifying the prerequisite query step. Could be slightly more explicit about the return format, but sufficient for a load operation.

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 100%, so the schema already documents both parameters. The description adds minimal extra meaning: it implies the 'name' comes from the query tool's results, but does not add details about format or constraints for the parameters.

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 verb 'load' and the resource 'checkpoint', specifying it loads the full body and bounded previews of linked notes, which distinguishes it from the sibling tool 'rms_checkpoint_query' that presumably lists or searches checkpoints.

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?

Explicitly advises to use 'rms_checkpoint_query' first to find checkpoint names, providing a clear prerequisite. However, it does not specify when not to use this tool or mention any alternatives beyond the prerequisite.

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