Critical gaps across all dimensions. Tool descriptions are minimal (10-30 chars), providing almost no context for LLM selection. No input schemas visible in source code, tools appear to be dynamically registered via dcc-mcp-core framework without explicit parameter definitions. Parameter descriptions entirely absent. Output schemas undocumented. Error handling and recovery guidance missing. Naming is acceptable (verb_noun pattern) but descriptions fail to explain WHAT each tool does, WHEN to use it, or what it returns. This server relies entirely on the dcc-mcp-core framework for schema generation, which is not visible in the provided source.

• Expand all tool descriptions to 50-200 characters. Example: 'krita.create_document' → 'Create a new Krita document with specified dimensions (width, height in pixels) and color mode (RGB, CMYK, Grayscale). Returns document_id for use in subsequent layer and export operations.'
• Document input schemas explicitly in tool registration. For each tool, specify required parameters with types (string, integer, enum), constraints (min/max, allowed values), and descriptions. Example: create_document(width: int [1-10000], height: int [1-10000], color_mode: enum[RGB|CMYK|Grayscale]).
• Document output schemas. Specify what fields each tool returns and their types. Example: create_document returns {document_id: string, width: int, height: int, color_mode: string}.
• Add confirmation/dry-run support for destructive operations. For delete_layer and flatten_document, add a 'confirm' parameter or implement a two-step pattern (preview changes, then execute).
• Remove or replace the ping tool. Use MCP capability negotiation (_meta.capabilities) in each request instead of a dedicated ping tool.