Single tool 'analyze_projected_costs' has a basic description but critically lacks a complete, visible input schema in the source code. The tool definition appears only in test files (test/e2e/server_test.go), not in the actual server implementation or design files. Input schema shows only PulumiJSON as a string with minimal description. No output schema is documented. No error handling guidance, no parameter validation rules, and no recovery paths are defined. The tool name is action-oriented (analyze_*) but the description is generic and under 100 chars. This server does not meet baseline quality for production use.

• Move tool definition from test file to design/design.go (Goa design DSL) with explicit schema, description, and parameter annotations.
• Expand tool description to 100-150 chars: state what it analyzes (Pulumi infrastructure costs), when to call it (after stack configuration), and what it returns (cost breakdown by resource type).
• Add input schema constraints: specify PulumiJSON format (JSON string, max length, required fields like 'resources' array), and add a second optional parameter for cost model selection (e.g., 'pricing_region').
• Document output schema with typed fields: e.g., { total_monthly_cost: number, resources: [{urn: string, type: string, estimated_cost: number}], currency: string }.
• Add error handling: return structured errors for invalid JSON, missing resources, unsupported resource types, and API failures (e.g., pricing service unavailable). Include recovery hints like 'Validate Pulumi JSON structure' or 'Check pricing service status'.