Hayhooks exposes two example tools from demo pipelines with minimal schema documentation. Both tools have descriptions and basic parameter definitions, but schema completeness is limited. The tool definitions appear to be inferred from example files rather than formally registered with full MCP server infrastructure. Input schemas are present but lack proper type declarations and comprehensive parameter descriptions. No documented output schemas. No error handling guidance. No tool annotations.

• Formally register both tools in the MCP server initialization code with complete input and output JSON Schema definitions. Document every parameter's type, required status, and constraints.
• Add documented output schemas showing all response fields. Example: suggest_activities should document 'activities' as an array of objects with 'name' and 'description' fields.
• Expand tool descriptions to 100-150 characters explaining WHEN to use each tool and how they compose. Example: 'Gets current weather (temperature, humidity, wind, condition) for a city. Use get_weather first, then pass weather_condition to suggest_activities.'
• Replace inline examples with formal constraints. Instead of 'e.g. Berlin', use a description like 'City name as a valid ISO 3166-1 country code + city name (2-100 chars)'. Instead of 'e.g. Light rain', define an enum: weather_condition (enum: [Clear sky, Light rain, Heavy rain, Snow, Clouds]).
• Add error handling guidance. Document: 'If city is not found, returns 404 with available nearby cities. If weather service is unreachable, returns 503 with cached weather data (age in seconds).'
• Implement pagination and result limits. If suggest_activities returns multiple activities, cap at 20 and document: 'Returns max 20 activities. Use limit and offset parameters for pagination.'
• Add tool annotations (readOnlyHint, idempotentHint) to both tools since they are READ_ONLY and safe to retry.
• Verify these are actual MCP server tools and not just example code. If they are examples for documentation, create a functional MCP server with proper tool registration in src/hayhooks/server/ or equivalent.