Single tool 'generate-wealthy-plan' has serious structural and documentation gaps. While the codebase shows good type infrastructure (ToolInputSchema, ToolOutputSchema with proper marshaling), the tool definition itself lacks sufficient description detail, has minimal parameter documentation, and provides no output schema validation. The input schema structure is present but parameter descriptions are generic placeholders ('Salary', 'Salary frequency Weekly, Semi-monthly, Monthly' rather than actionable LLM guidance). No evidence of error handling patterns, recovery guidance, or composition guidance for multi-step workflows. Tool name uses hyphenation (discouraged; verb_noun pattern preferred). No validation constraints (enums for frequency) visible in the schema. The Go type definitions show capability to declare OutputSchema, but no output schema is documented for the actual tool.

• Expand tool description from current ~45 chars to 100-200 chars. Template: 'Generates a financial plan based on the user's salary. Call when the user asks for budgeting advice, savings strategy, or income-based financial planning. Returns a structured plan with recommended allocations for expenses, savings, and investments.'
• Convert frequency parameter to explicit enum constraint. Update input schema: frequency type should be 'string' with enum: ['weekly', 'semi-monthly', 'monthly'].
• Define and document the output schema. Example structure: { type: 'object', properties: { plan: { type: 'array', items: { type: 'object', properties: { category: { type: 'string' }, percentage: { type: 'number' }, amount: { type: 'number' } } } }, total_monthly_income: { type: 'number' } } }
• Clarify salary parameter: 'Annual or periodic salary amount as a numeric value (e.g., 75000 for $75k annual salary). Required.'
• Add validation logic: reject negative salaries, non-numeric input, salaries >1000000 (or appropriate upper bound). Return errors in format: 'Invalid salary: got "<value>", must be a positive number less than 1000000.'
• Populate ToolAnnotations in the tool definition: at minimum, set readOnlyHint to true (this is a stateless planning tool).
• Rename tool from 'generate-wealthy-plan' to 'generate_financial_plan' (snake_case) or 'create_income_based_budget' (more specific action verb).
• Add dependency hint: 'If you do not know the user's salary, ask for it first. This tool requires a numeric income value.'

Inferred effective spec: 2025-06-18+.

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API