The create_issue tool lacks a visible input schema in the provided source code. The tool description is present but generic ('Creates an issue/task on the configured MCP platform'). No parameter definitions, type information, or output schema are documented in the accessible code. The tool appears to be registered in a Next.js API route rather than as a proper MCP tool definition with JSON Schema.

• Define create_issue as a proper MCP tool with explicit JSON Schema input and output. Example: { name: 'create_issue', inputSchema: { type: 'object', properties: { title: { type: 'string', description: '...' }, description: { type: 'string' }, platform: { type: 'string', enum: ['jira', 'trello', 'plane'] } }, required: ['title', 'platform'] } }
• Expand tool description to 100-200 characters explaining: (1) what it does, (2) when to use it vs alternatives, (3) what it returns. Example: 'Creates a task/issue on the selected platform (Jira, Trello, or Plane) from AI-generated requirements. Returns the external issue ID and platform-specific URL for follow-up operations.'
• Document all parameters with type, description, and constraints. For 'platform', use enum ['jira', 'trello', 'plane']. For 'title' and 'description', specify min/max length and required status.
• Document the output schema with fields like { externalId: string, platform: string, url: string, createdAt: string }. This enables agents to chain calls (e.g., pass externalId to add_comment).
• Add error handling guidance: 'If platform credentials are missing, return error with hint to configure MCP settings first.' Implement recovery patterns per pattern:recovery-guide.