spotify_get_artist_info

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

No annotations are provided, so the description carries full burden. It states 'get detailed information' but does not specify what 'detailed' includes (e.g., genres, popularity, followers). No disclosure of rate limits, authentication needs, or idempotency beyond the obvious read nature.

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?

Single sentence, 14 words, front-loaded with action and resource. No fluff. Every word 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?

Tool has one parameter and no output schema. Description is adequate for a simple lookup but lacks details on return fields. 'Detailed information' is vague; agent cannot anticipate response structure. Moderate completeness for 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% (artist_id is described as 'The Spotify ID of the artist'). The description adds no extra meaning beyond the schema. Baseline 3 applies; no value added.

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 verb ('get'), resource ('detailed information about a specific artist'), and the method ('by their Spotify ID'). It distinguishes itself from sibling tools like spotify_get_artist_name (only name) and spotify_get_artist_top_tracks (only tracks) by focusing on detailed info.

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 guidance on when to use this tool versus siblings. There are many artist-related getters (name, top tracks, albums, etc.) in the sibling list, but the description does not indicate when to prefer this tool for full details. No when-not or alternative suggestions.

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