Server has 7 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization) and input schemas with type definitions. However, parameter descriptions are minimal or absent, output schemas are undocumented, and error handling is missing. No tool annotations (readOnlyHint/destructiveHint). Responses are JSON-stringified text rather than structured objects. The server follows verb_noun naming (listBoards, createCard) but descriptions lack context on when to use each tool or what to expect in responses.

• Expand tool descriptions to 50-200 chars. Example: 'listLists' → 'List all lists (columns) in a Wekan board. Call this first to see available lists before creating or moving cards. Returns list ID and title.'
• Add parameter descriptions explaining format, constraints, and how to obtain values. Example: 'boardId: The unique identifier of the Wekan board (UUID format, e.g. from listBoards response).'
• Return structured objects instead of JSON-stringified text. Change 'JSON.stringify(boards.map(...))' to return { content: [{ type: 'text', text: JSON.stringify(...) }] } with a documented schema in the tool description.
• Add input validation and actionable error messages. Example: if boardId is invalid, return 'Invalid boardId format. Ensure it is a valid UUID from listBoards().' instead of a raw API error.
• Add tool annotations: destructiveHint=true for createCard/moveCard/commentCard; readOnlyHint=true for list* tools. This enables agents to reason about retry safety and side effects.