Two tools with complete input schemas and descriptions. Naming follows verb_noun pattern (draft_, create_). Schemas use Zod with proper types and descriptions. However, output schemas are undocumented, LLMs cannot predict response structure. Error handling is present but generic. No tool annotations (readOnlyHint/destructiveHint). Parameter descriptions are adequate (50-100 chars) but lack format constraints and validation guidance. Missing idempotency documentation for create_jira_issue.

• Document output schemas for both tools. Specify that draft_jira_issue returns {fields, command, description} and create_jira_issue returns {issue_key, url, ...}. Include field types and meanings.
• Add tool annotations: draft_jira_issue with readOnlyHint=true; create_jira_issue with destructiveHint=true. This signals to agents which tools are safe to retry.
• Enhance parameter descriptions with format constraints. E.g. 'projectKey (2-10 uppercase letters, e.g. NEO)', 'summary (max 255 chars)', 'priority (one of: Lowest, Low, Medium, High, Highest)'.
• Implement Multi Round-Trip Request pattern: draft_jira_issue returns a preview; create_jira_issue accepts confirmed=true only after user reviews the draft. Return result with input_required if confirmed=false.
• Standardize error messages to English and include recovery guidance. E.g. 'Jira CLI not found. Ensure jira CLI is installed and in PATH.' instead of generic German messages.