Two tools with partial schema definitions and inconsistent documentation. database_migration_tool has a complete input schema with 4 parameters, all typed and described. tool_roi_estimator has 13 parameters, all typed and described. However, neither tool has documented output schemas, which is critical for LLM planning. Descriptions are present but generic (194-char baseline suggests these are below average). No error handling guidance, no recovery paths, and no tool annotations. Tool names lack clear action verbs (database_migration_tool is noun-heavy; tool_roi_estimator is descriptive but not verb-first). No evidence of idempotency, pagination, or composition patterns.

• Add explicit output schema for database_migration_tool: return object with fields like 'analysis_results' (object), 'suggested_indexes' (array), 'migration_script' (string), 'rollback_script' (string), 'issues_found' (array of objects with severity and description).
• Add explicit output schema for tool_roi_estimator: return object with 'roi_timeline' (array of monthly projections), 'break_even_month' (number), 'minimum_traffic_needed' (number), 'projected_revenue_12m' (number), 'payback_period_months' (number).
• Rename tools to verb-first: 'analyze_database_schema' and 'estimate_tool_roi'. Update descriptions to start with action: 'Analyzes SQL schema files to detect issues...' and 'Estimates ROI of building a free marketing tool...'
• Add parameter defaults to tool_roi_estimator: traffic_growth_rate (default 0.10), tool_completion_rate (default 0.50), lead_capture_rate (default 0.05), months_to_model (default 12), seo_ramp_months (default 3).
• Add error handling guidance: 'If schema file is invalid SQL, returns error with line number and suggestion. If comparison file not found, returns error: "Comparison file required for 'compare' action."' Include recovery paths in descriptions.