GSAP Framework Integration

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

The description discloses key behavioral traits: it includes cleanup to prevent memory leaks, uses framework-specific lifecycle hooks (e.g., useLayoutEffect for React), and always generates code with cleanup. Since no annotations are provided, the description carries the full burden and does so adequately, though it could mention that it outputs code rather than modifying anything.

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 highly concise with two sentences: the first states the core purpose, and the second lists frameworks and patterns. Every sentence is informative, and no extraneous information is included.

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 nested parameters and complexity, the description covers the essential behavior thoroughly. It does not detail every option (e.g., scrollTrigger), but the schema covers those. It could mention the output format (e.g., returns code string), but overall it is sufficiently complete.

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?

With 100% schema coverage, the description adds meaning beyond the schema by explaining default integration types per framework (e.g., react defaults to hook) and the cleanup guarantee. This aids understanding without repeating schema details.

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 generates framework-specific GSAP integration boilerplate with proper cleanup, specifying the verb 'generate' and resource 'boilerplate'. It distinguishes itself from sibling tools like gsap_tween or gsap_timeline, which focus on animation logic, by being explicitly about integration setup.

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 clear context on when to use the tool (for integrating GSAP into React, Vue, Angular, or Svelte) and lists the integration types. However, it does not explicitly state when not to use it or mention alternative tools, though the sibling context makes the purpose clear.

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