GSAP ScrollTrigger

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. However, it only states what the tool does (animate on scroll) without revealing any behavioral traits such as DOM mutation, side effects, permission requirements, or rate limits. Key operational details are missing.

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 concise (3 sentences) and front-loaded with the core purpose. However, it could add brief parameter hints without becoming verbose. Minor deduction for not including any parameter guidance where schema coverage is zero.

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?

The tool is complex with 5 parameters, nested objects, and required fields, yet the description provides virtually no context on how to structure the animation, trigger, or batchOptions. Without an output schema, return behavior is also omitted. For this complexity, the description is severely incomplete.

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 0% schema description coverage, the description must compensate by explaining parameters. It does not; only the term 'scrub' is implied. No parameter syntax, allowed values, or usage examples are given. The description adds no semantic value over the bare 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 identifies the tool's purpose as animating elements based on scroll position using ScrollTrigger. It lists three specific use cases (scrub, pin, trigger-on-scroll) and explicitly distinguishes it from sibling tools (gsap_tween/gsap_timeline) for scroll-independent animations.

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 explicit guidance on when to use this tool ('scroll-driven animations, pin sections, trigger-on-scroll effects') and directs users to alternatives ('For scroll-independent animations use gsap_tween or gsap_timeline instead'). This provides clear context for tool selection.

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