Server has 8 tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error guidance. Most tools lack descriptions for individual parameters (e.g., search_issues has 'expand', 'fields', 'properties' with no descriptions). Descriptions are present but minimal (10-30 chars for most tools). No documented output schemas. Error handling returns raw text without recovery guidance. archive_issue has a logical error in its schema (both issueIdsOrKeys and jql marked required, but semantically only one should be needed). Tool names follow verb_noun convention (good), but parameter naming is inconsistent (userQuery vs issueKey).

• Add descriptions to every parameter in search_issues, create_issue, and edit_issue. Format: 'The [field name] to [action]. Valid values: [enum or range]. Example: [concrete example].'
• Document output schemas for all tools. Define what fields are returned, their types, and which are safe to chain into downstream tools. Use a structured format (JSON Schema or TypeScript interface).
• Enhance error messages with recovery guidance. Instead of 'Error retrieving issue', return 'Issue ABC-1 not found. Try search_issues() with a partial key or JQL query.'
• Fix archive_issue schema: make issueIdsOrKeys and jql mutually exclusive. Use oneOf or document that exactly one must be provided.
• Standardize parameter naming: use user_id, user_name, or user_email consistently across tools. Avoid overloaded 'userQuery', accept both ID and name with clear parameter names.