List snapshots

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

With no annotations, the description carries the full burden. It reveals that snapshots are on-disk and named, and scopes them to the selected model, but does not disclose read-only behavior, return format, or side effects. This is minimal transparency for a list operation.

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 (fragment) with no fluff or redundancy. It is concise and front-loaded with the key noun, though it could be a more complete sentence with a verb.

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 (no parameters, no output schema), and the description gives the essential context of on-disk and selected-model scope. However, it omits the explicit action and any indication of what the returned list contains, relying on the tool name for the verb.

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 zero parameters, so there is nothing parameter-related to explain. Baseline for zero parameters is 4; the description does not need to compensate for missing schema coverage.

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?

Description defines snapshots as 'named on-disk checkpoints' for the selected model, but does not explicitly state that this tool lists them. The verb 'list' appears only in the name/title, making the purpose somewhat vague, though the scoping to a selected model adds context.

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 is provided on when to use this tool versus alternatives like save_snapshot, restore_snapshot, or list_models. The phrase 'for the selected model' hints at a prerequisite but does not explain when listing is appropriate.

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