artist_scout_from_playlists

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

Annotations are completely absent, so the description carries the full burden. It discloses that the operation reads a playlist, scans items, and performs membership checks against saved tracks. It also flags quota cost with the 🔴 emoji. It does not specify side effects, but the term 'find new-to-you artists' plus 'membership check' implies a read-only discovery process. It transparently signals the two-pass operation (playlist walk + saved-track checks).

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 one compact sentence plus a short quota note. The core behavior is front-loaded, followed immediately by the differentiating value proposition. No redundant phrases. The quota signal earns its place as actionable information.

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's complexity is moderate: it takes one required playlist and several optional controls. The description covers the main workflow, the key qualifier (unsaved artists), and an important operational detail (quota). It doesn't describe the output shape, but there is no output schema and the response_format parameter covers output style. Minor gap: it doesn't mention whether the playlist must be owned by the user or whether any playlist works, but 'one of your playlists' implies ownership.

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 coverage is 100%, and the description does not add parameter-level detail beyond the schema. The parameters max_items, max_artists, playlist_id, and response_format are all documented in the schema. The description communicates the discovery semantics but not parameter-specific behavior such as defaults or how response_format interacts with output. Baseline 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 ('pull' and 'rank') and clearly identifies both the resource ('artist roster from one of your playlists') and the core value proposition ('artists you have NOT saved any tracks of'). The phrase 'discovery from your own rotation' further anchors intent. It distinguishes itself from sibling tools like saved_tracks_by_artist or playlist_artist_heat because it explicitly targets unsaved artists.

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 states that the input is a playlist from the user's own rotation and that the output is newcomers (unsaved artists). It implies this is the right tool for discovery from a playlist, but it does not explicitly say when NOT to use it or name alternative tools (e.g., discovery_digest for broader discovery, saved_tracks_by_artist for saved-artist stats). Still, it gives enough context for an agent to infer appropriate invocation.

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