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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety and determinism profile is covered. The description's only added value is naming the content domains returned (bio, sound description, releases, profiles, contact), which is modest but real context beyond the annotations.

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 compact sentence with the most useful information (what content is covered) front-loaded. It is a fragment rather than a sentence, but nothing is padded or repeated.

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 input parameters and no output schema, the description carries the full burden of explaining the return payload, and it only gestures at the content areas without saying what is actually returned or in what form. It is adequate to know roughly what the tool is about, but thin for a no-schema, no-param tool.

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 tool takes zero parameters, so the baseline of 4 applies; there is no parameter syntax the description could usefully add. The description neither contradicts nor omits any parameter information.

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 enumerates content areas (bio, sound, releases, profiles, contact) but contains no verb and never states the action, so it reads as a topic list rather than a tool purpose. The name 'get_artist' is generic while the title and description hardcode a single artist ('Boots & Bassline'), leaving the agent unsure whether this is a generic artist lookup or an artist-specific page. It is separable from the song/lyrics/list siblings by scope, but only implicitly.

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 statement of when to call this versus alternatives, even though siblings like get_listening_links, list_releases and find_song overlap with the 'releases, profiles and contact' content it advertises. No prerequisites, no exclusions, no routing guidance.

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