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

With no annotations, the description must carry the full behavioral burden, but it only says 'Artist search' and lists possible fields. It does not explain output shape, query handling, the effect of an empty q value, rate limits, or whether this is strictly a read operation, leaving significant behavioral ambiguity.

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 very short and front-loads the core idea, which is good. However, the leading 'MusicBrainz:' repeats the tool name and title, and the colon-separated fragment structure is telegraphic rather than organized, so the conciseness sacrifices needed clarity.

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 this is a simple one-parameter tool and an output schema exists, the description is not complete enough for correct invocation. The agent cannot tell what value to place in q, what 'type, country, MBID' refers to, or how this differs from musicbrainzartist, leaving a clear gap in selection and usage context.

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 input schema provides only a q string with a default value and 0% schema description coverage, so the description must explain how q is used. Instead, 'type, country, MBID' is not explicitly tied to q, and no format, separator, or example is given, making the sole parameter effectively uninterpretable.

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 states a clear purpose: search MusicBrainz artists, with search dimensions of type, country, and MBID. It is not a tautology because it names both the resource and operation, though it never uses a full verb phrase and does not distinguish itself from the sibling tool musicbrainzartist.

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 over alternatives, especially musicbrainzartist, which appears to be a closely related sibling. The description gives no exclusions, prerequisites, or example query context, so an agent cannot decide between tools based on the description.

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