Ultimate GSAP Master MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'expert optimizations' but lacks details on what these entail (e.g., code modifications, resource usage, side effects), response format, or limitations (e.g., supported animation types). This is inadequate for a tool that transforms code.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Transform any animation into 60fps smoothness') and adds a qualifier ('with expert optimizations'). There is no wasted text, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (transforming animation code), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'expert optimizations' involve, potential side effects, or return values, leaving significant gaps for an AI agent to understand the tool's behavior fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents the two parameters. The description adds no additional meaning beyond implying optimization for '60fps smoothness', which aligns with the 'target' enum but doesn't clarify parameter interactions or usage context beyond what's in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Transform', 'optimize') and resource ('animation'), and distinguishes it from siblings by focusing on performance optimization rather than creation, debugging, or learning. However, it doesn't explicitly differentiate from all siblings like 'debug_animation_issue' which might also involve performance aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing animation code), exclusions (e.g., not for creating animations from scratch), or comparisons to siblings like 'debug_animation_issue' for performance issues or 'create_production_pattern' for optimized patterns.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.