GSAP Timeline Creator

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

No annotations are provided, so the description carries the full burden. However, it only mentions building a timeline with tweens and labels, without disclosing any behavioral traits such as side effects, error handling, or what the output looks like. The agent is left without understanding what happens on invocation (e.g., whether code is generated or executed, or if there are any restrictions).

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 two sentences, front-loaded with the primary action and usage context. No unnecessary words, and it efficiently conveys the core purpose and differentiation.

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?

Despite the tool having a complex nested input schema with 5 parameters (including arrays and objects) and no output schema, the description provides minimal context. It doesn't explain the return value (likely generated GSAP code), nor does it give enough information for an agent to construct a valid timeline with the various sub-properties.

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 0%, so the description must compensate, but it only generically mentions 'tweens, labels, and position parameters.' It does not explain specific parameters like 'variableName', 'includeImports', 'settings', or the structure of 'animations'. The agent cannot infer parameter meaning from the description alone.

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: building a GSAP timeline with multiple sequenced or overlapping tweens, labels, and position parameters. It explicitly distinguishes from the sibling tool gsap_tween by noting when to use this tool (2+ animations) vs. a single animation.

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 gives explicit guidance on when to use this tool (for 2+ animations coordinated together) and when not to (for a single animation, use gsap_tween). This is sufficient for an agent to decide between siblings.

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