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

Despite annotations covering the safety profile (readOnly, idempotent, openWorld), the description goes well beyond: it demands credit attribution.line, mandates asking first when ambiguity.state is not none, flags untrusted_text as display-only, states 'Auth: linked', and caps tracks at 25 with include. This is rich operational and ethical context an agent needs.

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?

Front-loaded and labeled (Use/Inputs/Returns/Auth) with no wasted words; the telegraphic style is dense but readable. Slight compression makes a couple of labels terse, but nothing is padding.

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 return value explanation (data.master vs data.release, display-only titles, tracks cap) plus auth and ambiguity handling — largely complete. Minor gaps remain around which shape appears under the two ID paths, but overall sufficient to call correctly.

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 only 50% (master_id and bandcamp_item lack descriptions), but the description compensates: it explains key comes from resolve_artist or slug, adds the constraint that you pass one of master_id or bandcamp_item, and clarifies include:["tracks"] is Bandcamp-only and heavy. That adds meaning beyond the schema.

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 (a single release under an artist) and delineates the two subsystems, Discogs master (header, sections, artwork, freshness) vs Bandcamp release (facts, track list). It's clear what gets fetched, though it doesn't contrast itself with siblings like find_tracks or get_artist that might overlap.

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?

'Use: a discography row names the release; one specific release' clearly scopes it to a single known release rather than a listing/search. It doesn't explicitly name alternatives or exclusions, but the preconditions are stated.

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