Five tools with complete schemas and descriptions. Tool names follow verb_noun pattern (boutique_search, boutique_get, boutique_whats_new, boutique_request_coverage, boutique_coverage). Descriptions are detailed (100-250 chars) and include error codes. Parameters have types and descriptions. However, boutique_request_coverage and boutique_coverage lack parameter constraints (enums, ranges), and output schemas are not explicitly documented in the code. Error handling is structured with [code] prefixes but lacks recovery guidance beyond error names.

• Add enum constraint to boutique_search.entry_type: ['konektor', 'skill', 'kuratorski'] to prevent hallucinated values.
• Expand boutique_coverage description to explain when to call it (e.g., 'Call after boutique_search returns gaps[] to see what this connector does NOT cover') and document its output structure.
• Document output schemas for all tools. Add to tool docstrings: 'Returns: SearchResult with fields: hits (array of {id, name, install_command, card_url}), gaps (array of strings), provenance (object with source, date, stale flag)'.
• Enhance error messages with recovery hints. E.g., [not_found] for boutique_get should include 'Did you mean: <closest_ids>?' and suggest boutique_search() for discovery.
• Add limit constraints to boutique_search.limit parameter description: '1-25, default 10' is present but should be enforced with min/max in schema if JSON Schema is used.