Get a TIDAL artist

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that only 'public' metadata is returned, a useful scope note, but says nothing about auth requirements, rate limits, or behavior on missing IDs. With annotations carrying the burden, a mid score is appropriate.

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 tight sentence with the resource and scope front-loaded and no filler. It is efficient, though its brevity is partly the source of the coverage gaps elsewhere.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a lookup tool sitting among ~15 other artist-scoped getters, the description does not help the agent route among them or state how to obtain the required ID, leaving meaningful gaps.

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 single artist_id parameter has 0% schema description coverage, so the description must compensate. 'one exact artist ID' usefully clarifies that the input is an exact internal identifier rather than a name or search term, adding meaning beyond the bare string type, though it omits the format/length expectations already present in the schema's 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?

States a specific verb and resource ('Return public metadata') scoped to 'one exact artist ID', which is clearer than a bare name restatement. It does not, however, distinguish itself from the many artist-scoped siblings like tidal_get_artist_bio, tidal_get_artist_page, or tidal_get_artist_top_tracks.

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 phrase 'one exact artist ID' implies the agent must already hold a resolved ID (e.g. obtained from tidal_search) rather than a name, which is a weak usage hint. There is no explicit when-to-use, exclusion, or named alternative for the artist-lookup siblings.

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