save_artist_new_releases

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

With no annotations present, the description carries the full behavioral burden and does disclose the key mutation (saving albums to the library) and the deduplication safeguard (diffs against /me/library/contains, so only unsaved albums are affected). However, it does not disclose reversibility, what happens on partial save failure, whether singles/EPs are included, or any authentication/rate-limit considerations for a write operation.

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?

A single sentence with zero filler; the action verb is front-loaded, the scope is qualified, and the mechanism note is compressed into a parenthetical. Every element 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 compound read-plus-mutate tool with no annotations and no output schema, the core behavior is well covered, but the agent gets no expectation of the return value (e.g., how many albums were saved vs already in library) and no routing context against the many similar siblings. It is adequate for a basic call but leaves the agent guessing on outcome and disambiguation.

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 all four parameters, giving a baseline of 3. The description adds no parameter-level meaning beyond what the schema provides; it neither clarifies the market parameter's effect on 'new releases' nor the response_format enum's relationship to the save action.

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 compound action: find new releases for an artist and save unsaved albums to Your Library. The 'unsaved' qualifier plus the diff-against-/me/library/contains parenthetical makes the scope precise and distinguishes it from siblings like check_artist_releases or get_artist_albums, which only inspect.

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 when-to-use or when-not-to-use guidance is given, and no alternative sibling is named despite a large cluster of overlapping tools (check_artist_releases, watch_artists, save_release_radar, artist_release_digest). The purpose statement implies the use case (discover and save), but an agent is left to infer when this should be preferred over read-only release checkers.

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