load_snapshot

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

With no annotations provided, the description carries the full burden. It states that the tool loads a checkpoint as markdown, which implies a read operation, but does not explicitly confirm it is non-destructive or mention any side effects. The description is adequate but could be more explicit about the tool's safety profile.

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 with two sentences, no redundancy, and front-loads the core action. Every word adds value, making it easy for an AI agent to quickly grasp the tool's purpose.

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 simple tool with one parameter and no output schema, the description covers the main aspects: what it does, the input source, and the output format. It is nearly complete, though it could explicitly state that the operation is read-only.

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?

The input schema already describes the parameter 'id' with high coverage (100%). The description adds slight context by mentioning the id comes from list_snapshots or snapshot_session, but this is marginal. The baseline score of 3 is appropriate.

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'), the resource ('snapshot's full checkpoint'), and the output format ('as markdown'), making the tool's function unambiguous. It also distinguishes itself from siblings like list_snapshots by referencing it as the source for the id.

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 clear usage context: use after list_snapshots, and pass an id from that tool. It implies the use case of continuing a session. However, it does not explicitly mention when not to use it or list alternative tools besides list_snapshots.

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