Scoring was not performed

• Add full parameter descriptions to every tool. For each parameter, document: (1) what it controls, (2) valid format/range, (3) examples if applicable. E.g., 'issueType (integer): Jira issue type ID, 10001=Bug, 10002=Feature, 10003=Task. Retrieve valid types via listJiraIssueTypes.'
• Document output schemas for each tool. Specify returned fields, types, and what downstream tools can consume. E.g., 'createJiraIssue returns {issueId: string, key: string, url: string}' so attachFileToIssue knows it can use issueId.
• Replace catch-all exception handler with granular error responses. For user input errors, return 'Invalid {param}: got {value}, expected one of {enum}'. For retryable failures (timeout, rate limit), say so. For permission errors, guide to admin/auth.
• Add confirmation/dry-run support to deleteApiToken and deleteTestRuns. Return a preview of what will be deleted and require explicit confirmation before execution.
• Specify parameter constraints as enums or format strings. For issueType, define valid values. For webhookType and webhookOption, document the valid combinations.
• Add dependency hints. E.g., 'Note: if you only have an issue key (e.g., PROJ-123), call searchJiraIssues first to get the issueId.'
• Document authentication and permission requirements for each tool. E.g., 'Requires Jira project admin role and write:jira-issues scope.'
• Add pagination support to bulkCreateJiraTickets if issuesIds can be large. Document acceptable list size (e.g., max 100 per call).