Animotion MCP has 11 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search_, get_, list_, compose_, suggest_, upload_). Descriptions are present and contextual (avg ~120 chars). However, several tools lack output schema documentation, parameter descriptions are sometimes generic, and error handling guidance is absent. The compose_animation and suggest_animation tools accept free-form strings where enums would be more precise. No tool annotations (readOnlyHint/destructiveHint) despite clear read/write distinction. Custom icon upload is the only write operation but lacks confirmation/dry-run pattern.

• Document output schemas for all tools. E.g., search_animations returns {animations: [{id, name, category, css_class, description}], total_count, limit}. This enables LLMs to chain tools and extract the right fields.
• Add enum constraints to compose_animation: easing must be one of 'ease', 'ease-in', 'ease-out', 'ease-in-out', 'linear', 'cubic-bezier(...)'; duration/delay must match regex '^\d+(\.\d+)?(ms|s)$'.
• Add tool annotations: mark all read-only tools with readOnlyHint=true; mark upload_custom_icon with destructiveHint=true (modifies in-memory state).
• Add error handling guidance: 'If animation ID not found, call search_animations() to discover available animations.' Include this in tool descriptions and error responses.
• Implement confirmation pattern for upload_custom_icon: add optional 'dry_run' parameter that returns the icon preview without persisting, or require explicit 'confirm=true' parameter.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry