Five tools with consistent verb_noun naming (bandcamp_search, bandcamp_get_*) and clear, actionable descriptions (avg 95 chars). All tools have input schemas with typed parameters and enums where appropriate (e.g., search type, browse sort). Error handling is sophisticated, mapClientError() distinguishes NotFoundError, BandcampShapeChangedError, BandcampChallengeError, and BandcampUnavailableError, returning user-friendly guidance rather than raw errors. However, output schemas are not documented in the source, tool handlers return results but no schema definitions are visible. Parameter descriptions are present but minimal (e.g., 'Album slug in format...' lacks guidance on when to use this tool vs others). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Composition is clean, each tool has one responsibility, and search/browse tools support pagination (cursor parameter).

• Document output schemas for all five tools. Include field names, types, and descriptions. Example: bandcamp_search returns {results: [{title, artist, url, type}], total_count}.
• Add readOnlyHint: true to all tool definitions via registerTool() to signal safety and enable aggressive agent retries.
• Enhance parameter descriptions with dependency hints: 'Call bandcamp_search first to find an album slug, then pass it here.' This guides multi-step planning.
• Add regex pattern constraints to slug parameters: e.g., slug must match ^[a-z0-9-]+/[a-z0-9-]+(/[a-z0-9-]+)?$ to catch invalid formats early.
• Expand error messages with immediate next steps: 'Bandcamp rate-limited. Wait 60 seconds, then retry. If persistent, try bandcamp_browse_tag instead.'