get_artist

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered; the description adds that the result is 'full metadata' but does not expand on error behavior, rate limits, or result shape. This is acceptable for a trivial get-by-id operation but does not go beyond baseline.

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 no filler. The key information—what is returned and how the artist is identified—is front-loaded and complete.

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 fetch-by-id tool with an output schema present and read-only annotations, the description is nearly sufficient. It could be stronger by noting that artist albums are handled by get_artist_albums, but the core usage is not ambiguous.

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 0%, so the description must clarify the single parameter; it does so by specifying that artist_id is a Spotify id. This adds meaning beyond the schema's bare 'Artist Id' field, though it does not give format examples or validation constraints.

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 verb ('get'), a clear resource ('artist'), and the key qualifier ('by its Spotify id'). It is immediately recognizable as a single-artist metadata lookup and distinct from siblings like get_artist_albums or get_track.

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 clearly implies when to use it: when you already have a Spotify artist id and need the full metadata for that one artist. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for a simple lookup tool.

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