Server has 16 tools with basic structure but significant quality gaps. Most tools lack input schemas in the source code (only 4 tools show explicit schemas: get_work_item, list_work_items, create_work_item, update_work_item). Remaining 12 tools (get_boards, get_wikis, get_wiki_page, create_wiki, update_wiki_page, list_projects, list_pipelines, trigger_pipeline, list_pull_requests, get_pull_request, create_pull_request, update_pull_request) have no visible input schemas in the provided source. Descriptions are present but minimal (10-50 chars), lacking context on WHEN to use each tool or what it returns. No output schemas documented. Error handling exists but is generic ('Azure DevOps API error'). Tool names follow verb_noun convention (good), but parameter documentation is sparse or absent for most tools.

• Add explicit input schemas to all 12 tools lacking them (get_boards, get_wikis, get_wiki_page, create_wiki, update_wiki_page, list_projects, list_pipelines, trigger_pipeline, list_pull_requests, get_pull_request, create_pull_request, update_pull_request). Include parameter types, descriptions, and constraints.
• Expand all tool descriptions to 100-200 characters. Include: (1) what the tool does, (2) when to use it vs similar tools, (3) what it returns. Example: 'Get a work item by ID. Returns title, state, assignee, and links. Use this after list_work_items to fetch details. Supports custom fields via the fields parameter.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which are required for chaining (e.g., work_item_id for update_work_item). Include pagination fields (total_count, next_cursor) for list tools.
• Add pagination parameters (limit, offset/cursor) to all list tools. Cap results at 20-50 items by default. Document in descriptions: 'Returns up to 20 items. Use offset to paginate. Total count included in response.'
• Improve error handling: classify errors (retryable vs user-fixable), include the invalid value and constraint violated, and suggest recovery steps. Example: 'Invalid work item type: got "Epic", must be one of: Bug, Task, User Story, Feature. Call list_work_item_types() to see available types.'