Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. suggest_activities_under_price has a complex input (family dict, all_activities list) with minimal guidance on structure. distance_from_house is incomplete in the source (truncated). Neither tool documents output schema structure or error handling. Descriptions are present but generic (10 - 20 chars above minimum). No tool annotations (readOnlyHint, etc.). Parameter descriptions exist but lack format/constraint details (e.g., what fields must 'family' dict contain? What structure for activity dicts?).

• Add explicit JSON Schema definitions for 'family' and 'all_activities' parameters. Example: family should document {adults: int, children: [{age: int, name?: string}]}. all_activities should specify required fields like 'Activity Name', 'Base Price', 'Location', 'Min Age', 'Max Age'.
• Document output schemas for both tools. For suggest_activities_under_price, define the structure of each result object (activity, total_price, location, breakdown with nested adult/child cost details).
• Add error handling that returns structured feedback. Instead of silently skipping invalid activities, return {status: 'partial_success', skipped_count: N, errors: [{activity_name, reason}]} so LLMs know what failed.
• Complete the distance_from_house implementation in source code. The function is truncated, verify it returns a sorted list with distance values and all necessary fields for chaining (activity name, location, distance_km).
• Add tool annotations: set readOnlyHint=true for both tools in the FastMCP decorator (e.g., @mcp.tool(..., readOnlyHint=True)) to signal safety to agents.