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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds content context (data 'as on the profile', YouTube figures carry a measurement date), but says nothing about failure behavior for an unknown artist. With annotations carrying the behavioral load, a 3 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?

The purpose is front-loaded in the first clause, which is good. However, the sentence then becomes a long comma-chained enumeration of every returned field, and the bilingual Polish restatement repeats the same content, so much of the text does not earn its place alongside the output schema.

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?

For a one-parameter read tool with a full output schema and complete annotations, the definition covers what is needed to call it correctly and what kind of data comes back. Only the not-found and identifier-ambiguity cases are unaddressed, which is a minor gap at this complexity.

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?

Schema coverage is 100% and the single parameter's schema description already lists name, slug, and profile URL with an example. The description restates the same three accepted forms without adding format constraints or disambiguation rules, so it meets but does not exceed the baseline.

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+resource ('Profile of one artist on TopAIMuza.pl') and enumerates the content returned, so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling search_artists, which is the one thing an agent must infer.

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 description makes clear that this is a single-artist lookup keyed by name, slug, or profile URL, which implies usage as opposed to the plural search tool. But it never states when to prefer get_artist over search_artists, nor what happens if the identifier is ambiguous or missing.

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