list_saved_snapshots

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

With no annotations, the description carries the full burden. It does disclose that this is a listing operation with output fields and sorting, suggesting it is read-only. However, it does not explicitly state side-effects, what happens when no snapshots exist, or whether 'local' implies filesystem access or system requirements.

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 that efficiently conveys the core operation, ordering, output fields, and optional filter. Every phrase contributes useful information with no wasted words.

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 tool with no required parameters and no output schema, the description covers the main return content and ordering. However, the presence of `list_playlist_snapshots` as a sibling creates real confusion that this description does not resolve, and there is no mention of how `response_format` values affect the output semantics beyond the schema.

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 100%, so the schema already explains all three parameters. The description adds only a hint that filtering by playlist is possible, which is redundant with the schema. No additional meaning beyond the structured schema is provided.

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 uses a specific verb and resource ('List local playlist snapshots') and specifies ordering, returned fields, and optional filtering. However, it does not differentiate this tool from the similarly named sibling `list_playlist_snapshots`, which is a notable ambiguity.

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 given about when to use this tool versus alternatives like `list_playlist_snapshots` or `list_backups`. The optional filter is mentioned, but there are no explicit usage conditions, prerequisites, or exclusions.

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