Server has 17 tools with consistent naming (verb_noun pattern) and basic descriptions. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are often terse (10-50 chars), output schemas are not documented, and error handling lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Parameter descriptions are minimal, many lack format/constraint details. No pagination guidance in search results. Follows ~40% of the 54 patterns.

• Document output schemas for all tools. E.g., get_bug returns {bug_id, summary, status, assigned_to, ...}. Include required fields for chaining (bug_id for create_comment, attachment_id for update_attachment).
• Add tool annotations: mark create_bug, update_bug, create_comment, create_attachment as destructiveHint=true; mark all get_* and search_* as readOnlyHint=true.
• Enhance error messages with recovery guidance. E.g., 'Bug not found. Try search_bugs() with product and summary.' or 'API key missing. Set MCP_BUGZILLA_API_KEY environment variable.'
• Expand parameter descriptions with enums and constraints. E.g., severity: 'One of: blocker, critical, major, normal, minor, trivial' and priority: 'One of: P1, P2, P3, P4, P5'.
• Add pagination documentation to search_bugs. State: 'Returns up to limit results (default 20). Use offset for pagination. Response includes total_count for planning subsequent calls.'