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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile needs no repetition. The description adds genuinely non-structured behavior: the profile is computed only from an artist's top tracks (not the full catalog) and weights are 0-1 normalized, both of which affect interpretation of results. It omits edge-case behavior for unknown or partially resolvable artist IDs.

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 dense sentences with zero redundancy, and the payoff (what the profile contains) is front-loaded ahead of the batching limit. Every clause carries information an agent needs to interpret the response.

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 output schema, the description carries the burden of describing returns and does so concretely (genres, moods, activities with 0-1 weights, tempo min/avg/max). Minor gaps remain: the shape of the per-artist result and what is returned for an unresolved artist are unstated.

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 already documents accepted formats (IDs, URIs, URLs) and the 1-20 range. The description's 'Up to 20 artists per call' merely restates maxItems, so it adds no syntax or format meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 resource and the exact contents returned: genres, moods, activities with 0-1 weights, and tempo average/min/max BPM, derived from top tracks. This clearly separates it from a plain metadata lookup, though it never names the adjacent siblings (get_artist_overview, get_artists_stats) that an agent would otherwise have to disambiguate from.

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 when-to-use guidance at all: nothing explains when to pick this over get_artist_overview or get_artists_stats, nor any exclusion such as 'not suitable for full catalog analysis'. The only guidance-like sentence, 'Up to 20 artists per call', is a batching constraint rather than a selection rule.

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