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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds behavior beyond that: it enumerates the returned profile fields (name, location, bio, image) and states that the discography grid carries id/type/title/url that bandcamp_release accepts — a useful handoff contract. It is silent on pagination or partial/not-found behavior, so not a 5.

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, zero filler. Input contract is front-loaded, and the return/handoff information follows in the second sentence. Nothing repeats the title or the tool name.

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 an output schema present, annotations covering safety, and a single well-documented parameter, the description supplies what an agent needs: accepted identifier forms and a pointer to the downstream release tool. Minor gaps (label vs artist behavioral differences, pagination of large discographies) are not severe for a one-parameter lookup.

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 'artist' parameter already documents the subdomain-or-URL form with the same example. The description restates that syntax rather than extending it (no note on case sensitivity, trailing-slash handling, or custom-domain URLs). 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?

The description opens with a specific verb and resource — 'Get a Bandcamp artist or label page' — and immediately names the two accepted identifier forms (bare subdomain, e.g. theforeverwinter, or full https://{subdomain}.bandcamp.com URL). It also names the sibling it feeds (bandcamp_release), so an agent can distinguish it from bandcamp_release, bandcamp_discover, and bandcamp_filters without opening any schema.

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 clear by implication: this is the entry point for resolving an artist/label subdomain into profile data plus a discography whose ids are then consumed by bandcamp_release. There is no explicit when-not guidance (e.g. when to use bandcamp_discover or bandcamp_filters instead of looking up a known artist), which keeps it short of a 5.

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