sandbox_snapshot_listList saved sandbox snapshots for a project, including ID, name, template, region, size, scope, and status, to review and select snapshots for restore or audit.
List the saved sandbox snapshots of a project: ID, name, template, region, size, scope and status.
| Name | Required | Description | Default |
|---|---|---|---|
| project | Yes |
Changes observed during successful MCP inspections.
v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds the return field set, which is useful, but says nothing about pagination, ordering, or volume of results.
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 front-loaded sentence with the verb first and the return fields enumerated; 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?
With no output schema, listing the returned fields is genuinely helpful. However, for a list tool the description omits result volume/ordering and any hint that the project identifier format matters, leaving gaps an agent must guess at.
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 schema has one required parameter with 0% description coverage. The description's phrase 'of a project' loosely maps to it but does not say whether it accepts a project name, slug, or ID, nor any format constraints.
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 verb (List) and resource (saved sandbox snapshots of a project), plus the fields returned. It implicitly separates itself from sandbox_list (running sandboxes) and sandbox_snapshot (creation) but never names those siblings explicitly.
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?
No guidance on when to call this versus sandbox_list, sandbox_show, or sandbox_snapshot, and no prerequisites or exclusions. The agent must infer the distinction from the word 'snapshots' alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.