Game Factory has well-structured tool definitions with clear naming (verb_noun pattern) and complete input schemas. All 5 tools have descriptions and typed parameters with enums where appropriate. However, descriptions are brief (avg ~80 chars, below the 194-char baseline), parameter descriptions lack depth, and output schemas are not documented. Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. The 'act' tool definition location (src/landing/DemoGame.tsx) suggests it may be inferred rather than formally registered, capping its score.

• Document output schemas for all tools. Example for start_run: 'Returns {runRef: string, gameState: {hp, supplies, turn}, choices: [{id, label, risk}], narrative: string}'.
• Expand parameter descriptions with format/origin hints. E.g., 'runRef: Unique game session identifier returned by start_run. Format: UUID or alphanumeric string.'
• Add tool annotations to ListToolsRequestSchema response. Mark list_templates and export_challenge with readOnlyHint=true; mark start_run, act, end_run with destructiveHint=true.
• Enhance error messages with recovery paths. E.g., 'Invalid runRef: game session not found or expired. Call start_run() to begin a new game.'
• Verify 'act' tool is formally registered in src/server/index.ts with explicit toolDefinition export, not inferred from React components.