Server has 26 tools with complete JSON schemas and descriptions in Portuguese. Naming follows verb_noun pattern (create, update, delete, get, query, list). However, descriptions are often generic or lack actionable context for LLM selection. Many parameters lack type constraints (e.g., 'team' is a string with no enum or format). Output schemas are not documented. Error handling is minimal, no recovery guidance or categorization. Parameters like 'state' in create/update lack validation hints despite Azure DevOps having strict state machines per work item type. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Composition is reasonable (separate tools for CRUD), but some tools conflate concerns (e.g., create accepts both parentId and relatedWorkItemIds in one call).

• Add tool annotations: mark delete and delete-iteration with destructiveHint=true; mark create, update, create-iteration, create-team, create-wiki, create-wiki-page, update-wiki-page with destructiveHint=false and idempotentHint=false (or true if idempotent); mark all read-only tools with readOnlyHint=true.
• Document output schemas for all tools. E.g., create should return {id: number, url: string, type: string, title: string, state: string}. This enables agents to chain calls and extract IDs for follow-up operations.
• Enhance 'state' parameter descriptions in create and update. Add: 'Valid states depend on work item type and project process. Call get-work-item-states(type) first to discover valid states. Omit on create, Azure DevOps sets default state automatically.'
• Add error handling guidance to destructive tools. E.g., delete: 'Returns 204 on success. Returns 403 if user lacks permission (ask user for elevated access). Returns 404 if work item not found (verify ID with query or get). Returns 409 if work item is locked (retry after 30s).'
• Expand descriptions to 50-200 chars with actionable context. E.g., instead of 'Obter detalhes de um team específico', write: 'Fetch team details including members, area paths, and iterations. Use after list-teams to get full team config. Returns team ID, name, description, and member list.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry