backup_first

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

With no annotations provided, the description carries the behavioral burden. It discloses that the operation is read-only against Spotify, and that it creates a snapshot and returns a file path and counts. This is meaningful behavioral context beyond the schema.

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 with no waste: purpose is front-loaded, return behavior is stated, and the safety guarantee is succinctly provided. 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 one-optional-parameter tool with no output schema, the description covers what it does, when to use it, what it returns, and its safety profile. Slightly more detail about how the returned snapshot path relates to restore_library_snapshot would make it fully complete.

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 already fully documents the single optional 'notes' parameter, so the baseline applies. The description does not add extra meaning for the parameter, but none is necessary for an optional free-text field.

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 states a specific action ('Create a pre-flight library snapshot'), the resource ('library'), and the purpose ('before a destructive operation'). This clearly distinguishes it from read-only lookup tools and from playlist-focused snapshot tools in the sibling list.

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?

It explicitly says when to use it: before a destructive operation. It does not name alternatives like backup_library or list_backups, nor does it state when not to use it, but the timing guidance is clear enough for selection.

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