GSAP Animation Controls

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

With no annotations, the description takes full responsibility. It explains it outputs control code, requires a variable name, and lists actions. Could be more specific about output format (e.g., returns JavaScript string), but adequately covers core behavior.

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?

Three concise sentences front-load purpose, usage, and key clarifications. No wasted content.

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?

Description plus schema sufficiently cover purpose, parameters, and usage. Missing explicit return value description (no output schema), but the phrase 'Generate... code' implies the output. Overall adequate for an agent to select and invoke correctly.

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 covers 100% of parameters with descriptions. Description adds minimal value, e.g., examples for variableName and emphasis that it is not a CSS selector, but overall aligns with schema baseline.

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?

Description clearly states it generates playback control code for existing tweens/timelines, listing specific actions (play, pause, etc.). It distinguishes from sibling tools by directing users to gsap_tween/gsap_timeline for animation creation.

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?

Explicitly states when to use ('when you need runtime control over an animation you have already created') and when not to use (pointing to alternatives). No ambiguity.

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