Get an artist biography

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds one genuinely useful trait — the biography may not exist ('when available') — but says nothing about auth requirements, empty-result shape, or whether it hits a remote source.

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?

One short, front-loaded sentence with zero filler. It is efficient, though so terse that it omits information the tool actually needs.

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 the read-only profile. What is missing for a simple one-param tool is any guidance on argument sourcing and differentiation from the large set of sibling artist tools.

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 parameter has 0% schema description coverage, so the description carries the burden and contributes nothing: it never explains that artist_id is a TIDAL artist identifier or where one obtains it. Only the parameter's name hints at its meaning.

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 the artist biography text. That is unambiguous on its own, but it does nothing to distinguish itself from the many other tidal_get_artist_* siblings (get_artist, get_artist_page, get_artist_image), so an agent still has to infer which one answers 'tell me about this artist'.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only usage signal is the implicit 'when available', which tells the agent the result may be absent but not when to prefer this over tidal_get_artist or tidal_get_artist_page.

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