Four tools with minimal parameter descriptions and no output schemas documented. Tool names follow verb_noun pattern (repository_status, diff_summary, tofu_validate, ansible_syntax) but descriptions are terse (10-80 chars, below the 50-200 char LLM-optimized baseline). Only ansible_syntax has a parameter with description; the other three accept no parameters. No error handling guidance, no recovery paths, and no indication of what fields are returned. Audit logging is implemented server-side (good security practice) but not exposed to the LLM. No tool annotations (readOnlyHint, etc.) despite all being read-only operations.

• Add output schema documentation to each tool. E.g., repository_status returns {status: {exit_code: int, stdout: string, stderr: string, timed_out: bool, duration_ms: int}, recent: {...}}. Include field descriptions so LLMs know what to extract.
• Expand tool descriptions to 80-150 chars. E.g., 'Get current Git status and last 5 commits. Use this to check for uncommitted changes or recent deployments. Returns exit_code (0=success) and command output.'
• Add type and format constraints to ansible_syntax playbook parameter. E.g., type: string, pattern: '^[a-zA-Z0-9_/-]+\.(yml|yaml)$', description: 'Relative path to playbook file (must end in .yml or .yaml, no absolute paths)'.
• Document error recovery paths. E.g., 'If exit_code != 0, the validation failed. Check stderr for details. Common causes: syntax errors (fix and retry), missing dependencies (configure environment), timeout (increase validation_timeout in config).'
• Add readOnlyHint: true to all tool definitions via FastMCP annotations or schema metadata to signal to agents that these tools are safe to retry and do not mutate state.