Artist

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

Given annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, the description adds real value by disclosing that the call consumes paid credits, requires confirm=true, and that the read-like POST does not publish to social platforms. That reconciles the non-read-only hint with the tool's actual side effect (credit consumption, not state mutation).

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 purpose is front-loaded, but the same return fields (id, name, followers, genres, related artists) are listed twice in consecutive sentences, and the credit/confirm note is bundled into the same paragraph. Trimming the redundant second sentence would tighten it without losing 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?

With no output schema and no required parameters, the description sensibly enumerates the returned fields and covers the cost/confirm prerequisite, so an agent has what it needs to invoke the tool. Completion would benefit from clarifying id-vs-url precedence and the confirm gate's relationship to the individual call.

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 all four parameters (id, url, account, confirm) are already documented in the schema; the description adds no syntax or selection detail beyond it. Its reference to a 'handle' input does not map to any actual parameter, so it slightly muddies rather than enriches parameter understanding.

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 (retrieves) and resource (Spotify artist metadata) and enumerates the returned fields, which cleanly separates it from siblings like spotify_track or apple_music_artist. However, it says it looks up artists 'by their handle', yet the schema exposes only id and url, never a handle, which introduces a small mismatch.

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 flags the credit cost and the confirm=true prerequisite, which implies when the call is appropriate, but it never names alternatives such as spotify_search or explains when an agent should prefer this over another lookup route. Usage is implied by the cost warning rather than an explicit when/when-not statement.

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