SkyBuddy exhibits significant definition quality gaps. Tool names follow verb_noun convention (good), but parameter schemas are severely underdeveloped. The source code shows tool definitions with only string descriptions for parameters, no JSON Schema types, no enums, no constraints. For example, 'cabin_class' accepts 'economy/business/first' but is not declared as an enum; 'gender' accepts 'M/F/X' but lacks type info. Output schemas are completely undocumented. Error handling is absent, no recovery guidance, no categorization. Descriptions are present but generic (avg ~100 chars), lacking WHEN-to-use context and prerequisites. 23 tools with inconsistent quality; many lack parameter descriptions entirely (e.g., 'hours' in get_alerts has no description in the code snippet). No security patterns visible (no permission gates, no audit trails). Composition is reasonable (single responsibility per tool), but broken chains are likely, e.g., prepare_booking requires 'passengers' as array of names, but add_passenger returns no structured ID for chaining.

• Convert all parameter descriptions to formal JSON Schema: add 'type' (string, integer, number, boolean, array, object), 'enum' for constrained values, 'minimum'/'maximum' for numeric ranges, 'pattern' for format constraints. Example: {'type': 'string', 'enum': ['economy', 'business', 'first'], 'description': 'Cabin class for the flight.'}
• Document output schema for every tool. Specify returned fields, their types, and structure. Example for list_users: 'Returns array of {user_id: string, display_name: string, email: string, is_active: boolean}'. Include pagination info (total_count, next_cursor) for list tools.
• Add error handling with recovery guidance. For each tool, define expected error cases and actionable messages. Example: 'User not found. Try search_users() with a partial name.' Categorize as retryable, user-fixable, or fatal.
• Implement confirmation pattern for destructive operations. delete_user and confirm_booking should support a dry-run or require explicit approval. Return 'intent_id' for user confirmation before executing irreversible actions.
• Ensure tool chaining by returning all IDs needed by downstream tools. If add_passenger is called before prepare_booking, add_passenger must return a passenger_id or structured reference that prepare_booking accepts. Document these dependencies in descriptions.