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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only lists a few output fields and gives no indication of whether the tool performs a search, a direct lookup, or an external API call, nor does it mention error behavior, rate limits, or special constraints.

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 description is compact and contains no filler. However, it is under-specified rather than efficiently structured, reading as a title fragment rather than a clear functional description.

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?

Although the tool has only one parameter and an output schema exists, the description still fails to explain the input semantics or the relationship to the sibling `musicbrainz` tool. The minimal viability is only met if the agent makes assumptions about what `q` should contain.

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 `q` has zero schema description coverage and is not mentioned anywhere in the tool description. An agent cannot determine whether `q` should be an artist name, a MusicBrainz ID, or a free-text search query.

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 identifies the resource (MusicBrainz Artist) and the fields returned (type, country, lifespan), so the basic domain is clear. However, it lacks an explicit verb and reads more like a label than a functional definition. It also does not explicitly distinguish this tool from the sibling `musicbrainz` tool beyond the word 'Artist' in the name.

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 guidance on when to use this tool versus the sibling `musicbrainz` tool or any other artist-related lookup. The description implies an artist-focused lookup but never states the intended use case, exclusions, or alternatives.

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