Analyze Artists

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

With no annotations, the description must carry the behavioral burden, and it does disclose that this is a multi-call sampling operation (top N songs per artist) and what each sample contains. However, it says nothing about cost, latency, or failure modes for a request that can span up to 6 artists x 8 tracks, nor whether Last.fm tags or audio mood may be missing for obscure artists.

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 tight sentences, front-loaded with the core action before the interpretive guidance. No filler, though the second sentence's reading instructions could be trimmed if space were at a premium.

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?

No output schema exists, so the description must convey return values, and it does name the key fields (excerpts, average mood, tags, shared_tags). It stops short of describing the response shape - e.g. whether shared_tags is a cross-artist intersection - and gives no indication of what partial or empty results look like for artists with thin data.

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 both artists (1-6 names) and tracks_per_artist (1-8, default 5) are already documented in the schema with bounds and defaults. The description only echoes 'most popular songs' without clarifying how the sample is chosen or what happens at the 6-artist limit, so it adds little beyond the schema baseline.

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?

States a specific verb and resource: 'Sample each artist's most popular songs' and names the payload (lyrics excerpts, average audio mood, Last.fm tags). It also frames the analytical goal - find commonality across artists - which distinguishes it from retrieval siblings like get_artist_tracks or get_track_profile, though it never names those siblings explicitly.

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?

Gives a concrete motivating use case ('why do I like these artists?') and instructs how to consume the results: read excerpts for themes, imagery, perspective and tone, use shared_tags and mood averages for the musical side. It lacks explicit when-not-to-use guidance or a pointer to alternative tools for single-artist or single-track lookups.

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