spotify_play_artist

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

No annotations are provided, so the description must carry the full behavioral burden. It states the tool plays music (implying a side effect on playback) but does not mention prerequisites like authentication, behavior on artist not found, or whether it interrupts current playback. This is a significant gap for a mutation tool with zero annotation coverage.

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, front-loaded with the action and includes a clarifying example. Every word earns its place; there is no fluff or redundancy.

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 one-parameter tool, the description is minimal. It omits authentication requirements (given the sibling auth tools), playback behavior (e.g., stopping current track), and error handling. No output description is provided. This is incomplete for a mutation tool with no annotations to fall back on.

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 fully documents the single 'artist' parameter (100% coverage). The description adds that the artist is used to search and play their songs, which reinforces the schema but does not add format or syntax details. Baseline 3 is appropriate since the schema already handles the parameter semantics.

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 clearly states the action: search and play songs by a specified artist, with a concrete example ('Taylor Swift的歌曲'). It distinguishes from the sibling spotify_play_song (which likely targets a specific song) by focusing on artist-based playback, giving a specific verb+resource pairing.

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 implies the tool is for playing an artist's songs but does not explicitly state when to use this vs spotify_play_song or other playback controls. There is no mention of alternatives or exclusion conditions; the example offers context but no routing guidance.

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