playlist_history

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

With no annotations provided, the description carries the full behavioral burden. It explicitly discloses that the operation is read-only and makes no API calls, which are important behavioral traits. It also clarifies the data comes from local backup_now snapshots rather than live Spotify data.

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?

Two sentences, no wasted words. The core purpose and output fields come first, and the entry-point relationship plus read-only/no-API-calls behavior follow naturally. Every sentence earns its place.

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 low-complexity listing tool with fully documented parameters, the description provides the essential output fields and behavioral context. The only minor gaps are ordering, pagination behavior, and the exact meaning of 'counts,' but these are not critical for selecting and invoking the tool.

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 documents max_results and response_format. The description adds context about the returned snapshot fields but does not add new meaning about the parameters themselves, so the baseline score of 3 is appropriate.

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 your local backup snapshots') and names the exact output fields (file name, created timestamp, counts). It also distinguishes itself from sibling snapshot tools by identifying itself as the entry point for snapshot_detail / changelog / clone_snapshot.

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 description clearly indicates when to use it: as the entry point before snapshot_detail, changelog, or clone_snapshot. It also states it is local, from backup_now, and read-only, which helps an agent choose it over API-backed or mutation tools, though it doesn't explicitly exclude sibling listing tools like list_backups.

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