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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words elsewhere: typo tolerance, the result cap, and the ordering rule when only a genre is supplied. That ordering rule is genuinely useful behavior not derivable from the schema. It stops short of saying what an unfiltered call returns or how partial matches are ranked when both query and genre are given.

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?

Two tight sentences with the core action and the return shape front-loaded, plus one ordering caveat that earns its place. The full bilingual duplication nearly doubles the length for no added information, which costs a point.

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 carry the safety semantics. The remaining gap is the zero-parameter case (all three params are optional) — the description never says whether an empty call returns all artists or fails.

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%, so the baseline is 3; the description earns above that by adding fuzzy matching semantics for the name ('typos tolerated') and by clarifying that genre-only queries sort by chart position, which explains how the optional parameters interact.

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 ('Search AI music artists in the TopAIMuza.pl catalogue by name ... and/or genre'), which is immediately actionable. It does not contrast itself with siblings like get_artist or search_tracks, so an agent must infer that this is the list/search variant rather than the detail lookup.

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?

Usage is implied by the phrase 'by name (typos tolerated) and/or genre', which tells the agent the two valid entry modes, but there is no explicit 'use this instead of X' routing, no statement about what happens with zero arguments, and no exclusions.

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