Warhammer Oracle has 14 tools with consistent naming (verb_noun pattern: lookup_, search_, compare_, determine_, calculate_) and reasonable descriptions (100-200 chars typical). All tools are read-only, lowering error-handling complexity. However, schemas are inferred from smoke-test references rather than directly visible in source, and parameter descriptions lack domain-specific constraints (e.g., game_mode enum values are mentioned but not formally defined). Output schemas are undocumented. The wound_calculator tool is notably complex with 10 parameters but lacks guidance on parameter interdependencies and expected output structure. No tool descriptions include WHEN to use vs. alternatives, and no error recovery guidance is present.

• Add explicit output schema documentation to every tool. For example: lookup_unit should document that it returns {unit_name: string, faction: string, game_mode: string, points: number, weapons: array, stats: object, keywords: array, description: string}.
• Convert informal enum constraints to JSON Schema enums. Replace 'game_mode: wh40k_10e, wh40k_11e, combat_patrol, or kill_team' with proper schema: {enum: ['wh40k_10e', 'wh40k_11e', 'combat_patrol', 'kill_team']}.
• Add tool annotation hints (readOnlyHint: true) to all tools via the schema. This signals safety to hosting agents.
• Differentiate lookup_unit (exact match) vs. search_units (partial match) in descriptions. Add: 'lookup_unit: Use when you have the exact unit name. search_units: Use when you have a partial name or want to explore available units.'
• Document wound_calculator output structure and parameter interdependencies. Example: 'Parameters strength and toughness determine base hit. weapon_keywords (e.g., Devastating Wounds) modify damage rolls. Returns {total_hits, total_wounds, total_damage, wounds_per_model_killed, models_killed}.'
• Add error recovery paths to lookup tools. Example: 'If unit not found, this tool returns {status: not_found, suggestions: [similar_unit_names]}. Call search_units() with the unit's faction to find valid names.'
• Document whether faction and game_mode parameters are case-sensitive and what happens if they don't match any data (e.g., partial match vs. exact match vs. error).
• Add min/max constraints to numeric parameters. For wound_calculator: attacks (1-100), hit_skill (2-6), toughness (1-10), armour_save (2-6), damage (1-6 or 'D3'/'D6'), wounds_per_model (1-20).