All three tools have generic, undescribed input schemas with no parameter-level documentation. Tool names lack action verbs (calendar, task_manager, notes are nouns, not verb_noun patterns). Input schemas use generic 'action' and 'payload' fields instead of explicit, typed parameters. No output schemas documented. Descriptions are present but vague (e.g., 'Supports syncing calendar events' lacks WHEN/WHY/HOW context). No error handling guidance. This is a dispatcher pattern masquerading as MCP tools, the actual tool logic is hidden behind string-based action routing, making it impossible for LLMs to understand what parameters each action accepts.

• Rename tools to action verbs: sync_calendar_events, create_task_from_goal, capture_notes. Register each as a separate tool with explicit input schemas.
• For each tool, define a complete JSON Schema with typed parameters. Example: sync_calendar_events should have intent (string, required), timeframe (enum: 'today'|'this_week'|'this_month'), and optional context fields.
• Add parameter-level descriptions. E.g., 'intent (string, required): Natural language description of the calendar action (e.g., "Schedule a meeting with the team on Friday").'
• Document output schemas. E.g., sync_calendar_events returns {events: [{id, title, start, end, attendees}], sync_status: 'success'|'partial'|'failed'}.
• Add error handling guidance. E.g., 'If timeframe is invalid, returns {error: "Invalid timeframe. Must be one of: today, this_week, this_month", suggestion: "Try 'this_week' for upcoming events"}'