Server has 4 tools with clear verb-noun naming (deploy_*, get_*, list_*). All tools have descriptions (194 - 250 chars, within baseline 34 - 392). Input schemas are present with type definitions and descriptions. However, output schemas are not documented, responses are inferred from code inspection. Error handling is minimal; tools return raw HTTP status codes without recovery guidance. Parameter descriptions lack format constraints (e.g., 'days' accepts 1 - 365 but this is not stated). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE vs READ_ONLY). Missing pagination guidance for list_recent_runs despite accepting a 'limit' parameter.

• Add explicit output schema documentation for each tool. Example for deploy_fabric_workspace: 'Returns {queued: bool, target_env: str, ref: str, note: str, likely_run: {id: int, status: str, created_at: str} | null}'.
• Annotate tools with readOnlyHint/destructiveHint. Add @mcp.tool(readOnlyHint=True) to get_run_status, list_recent_runs, get_deploy_trends. Add destructiveHint=True to deploy_fabric_workspace.
• Enhance error messages with recovery guidance. Replace 'status_code: 403, error: ...' with 'Workflow dispatch failed: GitHub API returned 403 Forbidden. Verify GITHUB_TOKEN has Actions:write scope on {GITHUB_OWNER}/{GITHUB_REPO}. See https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token'.
• Add numeric constraints to parameter descriptions. Change 'days: Trailing window size in days (default 30)' to 'days: Trailing window size in days (1 - 365, default 30). Values outside this range will be clamped.'
• Document pagination for list_recent_runs. Add to description: 'Returns up to `limit` runs (max 100). Response includes total_count and next_cursor (if more results exist). Use next_cursor in a follow-up call to fetch the next page.'