list_saved_snapshots

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

No annotations are provided, so the description carries the disclosure burden; it covers ordering (newest first), locality (local), and the returned fields (path, creation time, size, _meta). This is enough for a simple list operation, though it doesn't explicitly state that no mutation occurs.

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 core listing behavior and output fields are front-loaded in a single sentence, and the snapshot guide is compactly organized by operation. The guide adds length but earns its place by orienting the agent in a large sibling toolset.

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 read-only list operation with no output schema, the description gives the essential calling context: what it lists, the order, the fields, and the optional filter. The remaining details (max_results default, response_format values) are already in the input schema, so nothing critical is missing.

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 coverage is 100% and the three parameters already have clear descriptions/types/defaults. The description adds only that filtering by playlist is optional, aligning with the playlist parameter but not going beyond the schema.

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'), a clear resource ('local playlist snapshots'), ordering, and the fields returned. It also orients the tool within a snapshot workflow guide, though it does not distinguish it from the similarly named sibling list_playlist_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 embedded snapshot guide explicitly maps related tools to create/list/read/diff/restore roles, so an agent knows what this tool is for relative to siblings. It says the listing can be filtered to one playlist, but it doesn't state explicit when-not-to-use conditions or address the closely named list_playlist_snapshots.

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