FrontForge has 7 tools with clear naming (verb_noun pattern) and reasonable descriptions (avg ~150 chars). All tools have input schemas with types and descriptions. However, output schemas are not documented, LLMs cannot predict what fields to expect from tool results. Error handling is absent; tools do not guide recovery or categorize failures. Parameter descriptions lack format constraints (e.g., 'PascalCase' is stated but not validated). No tool annotations (readOnlyHint/destructiveHint) despite 6 of 7 being destructive WRITE operations. Composition is sound, tools chain well (project_info → scaffold_project → create_feature), but missing idempotency guarantees and confirmation patterns for irreversible operations.

• Add output schemas to all tools. Document the structure of returned objects (e.g., scaffold_project returns {paths: {features: string, providers: string, ...}, created: boolean, errors?: string[]}). This enables LLMs to chain tools and extract required IDs/paths.
• Implement structured error responses with actionable recovery hints. E.g., if featureName is invalid, return {error: 'Invalid featureName: got "landing-page", expected PascalCase (e.g., "Landing"). Try: create_feature(featureName="Landing", ...)'} instead of a generic failure.
• Add tool annotations to all destructive tools. Set destructiveHint=true on scaffold_project, create_feature, create_component, setup_query_provider, create_query_hook, create_style. Set readOnlyHint=true on project_info. This signals to LLMs which tools modify state.
• Implement a dry-run or confirmation pattern for scaffold_project and create_feature. Add an optional 'confirm' parameter or return a confirmation request (MRTR pattern) before overwriting directories. E.g., if features/ exists, return {status: 'input_required', message: 'Directory features/ already exists. Overwrite? (yes/no)'}.
• Add regex patterns and validation to parameter descriptions. E.g., featureName: {type: 'string', pattern: '^[A-Z][a-zA-Z0-9]*$', description: 'Feature name in PascalCase (e.g., "Landing", "Dashboard"). Must start with uppercase letter.'}. Validate on the server and return clear errors if violated.