SnapKitty MCP server has well-structured tool definitions with complete JSON schemas and descriptions, but suffers from critical naming and composition issues. Tool names lack action verbs (worm_seal, worm_read, twin_chat are acceptable; agent_build, ada_contract_generate, injection_spec_generate are vague). Descriptions are present but generic, they explain WHAT without guiding WHEN to use each tool. Parameters have types and descriptions, but several lack constraints (e.g., 'label' in worm_seal accepts any string; 'capabilities' array has no item constraints). Error handling is minimal, no recovery guidance, no retryability classification. The server conflates multiple concerns: worm_seal both writes AND seals (two operations); agent_build creates AND seals; ada_contract_generate generates AND seals. This violates single-responsibility and forces agents to reason about side effects. Output schemas are partially documented but lack pagination, result limits, or chaining IDs. Security: no mention of permission gates, audit trails, or input sanitization for untrusted agent payloads.

• Rename tools with clear action verbs: 'create_agent_manifest' (not 'agent_build'), 'generate_ada_contract' (not 'ada_contract_generate'), 'generate_injection_spec' (not 'injection_spec_generate'). Verb-noun naming lets LLMs parse intent from the name alone.
• Split compound operations: separate 'seal_payload' (write to WORM) from 'create_agent_manifest' (generate manifest). Let agents compose them. This follows single-responsibility and makes side effects explicit.
• Enhance descriptions with WHEN-to-use guidance. E.g., 'Use worm_seal to record immutable audit events (deployments, decisions, contracts). Call this AFTER an action completes to create a tamper-evident record. Returns the SHA-256 seal hash for verification.'
• Add error handling and recovery guidance. Document what happens if Ollama is unreachable, WORM file is corrupted, or a model does not exist. Provide actionable error messages: 'Model nemotron not found. Available models: [list]. Install via ollama pull <model>.'
• Constrain parameters with enums, patterns, and length limits. E.g., 'label' should be an enum (DEPLOY, DECISION, CONTRACT, etc.) or a pattern (alphanumeric, max 32 chars). 'capabilities' items should be validated against a known set. Add min/max for numeric params.