taste_checkpoint

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

With no annotations provided, the description carries the full disclosure burden and does real work: '2 reads, sidecar write only' tells the agent the call costs two reads and never mutates Spotify account state, only a local dated sidecar slot. This is a meaningful safety-transparency signal beyond the schema. It stops short of disclosing label-collision/overwrite behavior, but the core side-effect profile is clear.

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 totaling roughly 30 words, with the action, storage location, and purpose front-loaded and the cost/side-effect note in the second sentence. No filler; every clause 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 simple tool with 0 required parameters, 100% documented schema, and no output schema, the description covers purpose, storage target, cost, and companion workflow. The only notable omissions are overwrite behavior for an existing label and what the tool returns, but these are minor given the low complexity.

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% — label, time_range, and response_format each have inline descriptions with defaults and enums — so the baseline is 3. The description itself adds no parameter-level detail beyond the schema, though 'current top artists/tracks/genres' loosely echoes the top-list window concept.

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-resource pair ('Save a snapshot of your current top artists/tracks/genres') plus an explicit purpose ('longitudinal taste tracking') and names the companion tool (taste_checkpoint_diff). This clearly differentiates it from sibling storage tools like backup_library, snapshot_playlist, and save_playback_state.

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 phrase 'for longitudinal taste tracking' supplies clear usage context, and '(pair with taste_checkpoint_diff)' tells the agent which sibling completes the workflow. It does not explicitly enumerate exclusions, such as when to prefer backup_library or get_top_tracks, but the purpose framing makes the intended use unambiguous.

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