Azure Board MCP has 30 tools with consistent naming (verb_noun pattern) and descriptions present for all tools. However, parameter descriptions are often generic or missing detail. Input schemas are visible but lack depth, many parameters lack type constraints (enums, ranges, patterns). Output schemas are not documented. Error handling includes helpful hints but lacks structured recovery guidance. The server follows basic patterns but misses production-grade rigor in parameter validation, output documentation, and error classification.

• Document output schemas for all tools. For list_work_items, specify: returns array of {id, type, state, title, assignedTo, sprint, points, priority}. For get_work_item, specify full field set including relations.
• Convert parameter constraints to JSON Schema enums. E.g. 'status' in list_pull_requests: enum=['active','completed','abandoned']. 'kind' in list_paths: enum=['area','iteration'].
• Add format/range descriptions to numeric and path parameters. E.g. 'priority: integer 1-4 (1=highest)'; 'iterationPath: backslash-separated path, e.g. MyProject\Sprint1'.
• Implement confirmation pattern for destructive operations. Add optional 'dryRun' boolean to cancel_build, run_pipeline, create_release. Return what would happen without executing.
• Enhance error responses with classification. Return {error, category: 'retryable'|'user_fixable'|'fatal', suggestion}. E.g. 'User not found (user_fixable): Try search_users() with partial name.'