snapshot_library

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

With no annotations provided, the description must carry the behavioral burden. It discloses that the tool writes a snapshot to disk and that it enables changes_since, which are useful side effects. However, it does not clarify label behavior, whether snapshots are named automatically, whether existing snapshots are overwritten, or what the tool returns.

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 with high information density. The main action is stated up front, and the two ancillary details (backup and enabling changes_since) are integrated without waste.

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: one optional parameter, no output schema, no annotations. The description explains the core operation and the implied prerequisite for changes_since. It is largely complete, but the lack of any description of 'label' prevents a perfect score.

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?

There is one parameter, label, and the description says nothing about it. Schema description coverage is 0%, so the description needed to explain the meaning and purpose of label but did not. An agent cannot know why they would supply a label or what format/constraints apply.

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 verb (Save), a specific resource (full snapshot of all playlists + liked songs), and the destination (disk). It also explains the purpose (backup; enables changes_since), which distinguishes it clearly from siblings like list_snapshots or changes_since.

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 implicitly tells the agent this should be run before using changes_since and positions the tool as a backup operation. It doesn't explicitly name alternatives or say when not to use it, but the context is clear and sufficient for this simple tool.

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