Five tools with consistent naming (verb_noun pattern: fetch_*, search_*, get_*) and complete input schemas. All tools have descriptions (10-60 chars, below the 50-200 char LLM-optimized baseline). Parameters are typed and described. However, output schemas are not documented, LLMs cannot plan downstream calls or extract fields. No error handling guidance. All tools are READ_ONLY, reducing risk but limiting utility. Tool names are clear but descriptions are minimal (e.g., 'Fetch normalized details for a single campaign' lacks context on when to use vs search_campaigns).

• Expand tool descriptions to 80-150 chars. Example: 'mautic_fetch_campaign' → 'Fetch full campaign details including name, status, events, and segment info. Use this after search_campaigns to get details for a specific campaign ID.'
• Document output schemas for all tools. Specify returned fields (e.g., campaign: {id, name, status, events: [{id, name, type}]}) so LLMs know what data is available.
• Add error handling guidance: 'If campaign not found, try search_campaigns() with a partial name. If API fails, retry after 5 seconds.'
• Add readOnlyHint annotations to all tools in the McpTool attribute to signal safety to clients.
• Enhance parameter descriptions with constraints: 'limit (1-100, default 10)' and 'page (1+, default 1)' to guide LLM input.