deckproof-mcp has clear, domain-specific tool names (pptx_*) and reasonable descriptions (avg ~120 chars). All 5 tools have input schemas with type definitions. However, parameter descriptions are sparse or missing entirely, most params lack guidance on format, constraints, or when to use them. Output schemas are not documented. Error handling is minimal. The server follows a sensible composition pattern (list layouts → create deck, validate, audit, repair) but lacks the LLM-optimization details (enums, constraints, recovery guidance) expected of production tools.

• Add enum constraints to pptx_create_deck's 'archetype' parameter. List all 15 valid archetypes (cover, contentBullets, dataTable, etc.) as an enum in the schema and reference them in the description.
• Document output schemas for all tools. E.g. pptx_list_layouts should return {archetypes: [{name: string, description: string}]}; pptx_create_deck should return {file: string (base64), size: number, validation_passed: boolean}.
• Expand parameter descriptions with format and constraint details. E.g. 'template: Base64-encoded .pptx file (max 50MB). Required for bring-your-own-template mode; omit for generic theme.' and 'slides: Array of slide objects. Each must have archetype (string, one of: cover, contentBullets, ...) and optional stencilSlideIndex (0-based integer, template mode only).'
• Add mutual exclusivity notes. E.g. 'pptx: Base64-encoded file (HTTP mode). path: Local filesystem path (stdio mode only). Provide exactly one; if both are given, pptx takes precedence.'
• Include error recovery guidance in descriptions. E.g. 'If validation fails, call pptx_repair to fix spec violations automatically, then re-validate.' and 'If the file is unreadable, ensure it is a valid .pptx (ZIP archive with OOXML structure).'