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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real behavioral value on the response side — it warns that results carry status, coverage dates and limitations, that unavailable/stale status must be preserved, and that a missing metric must not be read as zero. It does not mention auth or rate-limit behavior, so it is strong but not exhaustive.

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 sentences, no filler, with the trigger condition front-loaded. The second sentence packs status/coverage/limitations and the missing-metric caveat into one dense clause chain, which is slightly heavy but each element earns its place.

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 enumerated, and the description still adds interpretation guidance about status and missing metrics. Combined with clear triggers and domain scoping, an agent has enough to invoke it correctly; only the artistId source/format and sibling disambiguation are left implicit.

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?

There is one parameter (artistId, UUID) at 0% schema description coverage, and the description never mentions it or explains that it must be the artist's UUID from dynamoi_list_artists. With a single obvious identifier this is a minor gap, but the description contributes nothing beyond the schema here.

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 names concrete outputs — monthly listeners, listener growth over time, growth audit/score, playlist reach, and growth recommendations — so an agent can tell what the tool returns. It also carves out a domain boundary ("Spotify and market insight data, not paid campaign performance"), which separates it from campaign siblings, though it does not distinguish itself from dynamoi_get_artist_analytics or dynamoi_get_audience_analytics.

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?

It gives an explicit trigger clause ("Use this when the user asks for...") with several concrete user phrasings, plus an exclusion for paid campaign performance data. It stops short of naming the alternative tool an agent should call instead for adjacent questions.

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