Retrieve snapshots captured from a specific sandbox session to inspect or revert to prior states.
List the snapshots captured from a specific sandbox session.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | ||
| page_token | No | ||
| session_id | Yes | Sandbox session id (UUID), from tenki_create_sandbox or tenki_list_sandboxes. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds no extra behavioral context such as pagination semantics, ordering, or authorization requirements beyond the obvious 'list' behavior.
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 sentence communicates action, resource, and scope with no filler. The description is front-loaded and every word contributes to meaning.
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?
The tool is simple and annotations cover the behavioral safety profile, but the description omits guidance on response shape and pagination parameters. With no output schema provided, an agent must infer these details.
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 only 33%, so the description must compensate for undocumented parameters. It restates the session scope, but does nothing to explain page_size or page_token, leaving those parameters semantically incomplete.
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?
Names a concrete resource ('snapshots') with an action ('List') and a clear scope ('from a specific sandbox session'). This distinguishes it from sibling tools like tenki_list_workspace_snapshots and tenki_list_dangling_snapshots.
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 phrase 'from a specific sandbox session' clearly establishes the selection context: use this tool when snapshots tied to one session are needed. It does not explicitly name alternatives or when-not-to-use conditions, so it does not reach a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.