gsap-parallax

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

Without annotations, the description must disclose behavioral traits, but it only states the tool creates parallax effects. It does not mention scrolling triggers, performance implications, or any side effects, leaving the agent with minimal information.

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 sentence that front-loads the purpose. It is concise with no wasted words, though it could be slightly expanded for additional clarity without losing conciseness.

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 (parallax scrolling often involves multiple parameters like speed, direction, or trigger), the description is insufficient. No output schema exists, and the description fails to cover typical behavior like scroll-triggered animation or element movement.

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?

The schema already describes the single parameter ('CSS selector for parallax elements') with 100% coverage. The tool description adds no additional meaning beyond restating the tool's purpose, so it meets the baseline but adds no value.

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 verb 'Create' and the resource 'parallax scrolling effects', distinguishing it from sibling tools like gsap-animate or gsap-draggable. However, it lacks specificity about what kind of parallax effect or how it's applied.

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?

No guidance is provided on when to use this tool over alternatives like gsap-animate or gsap-stagger. Given the sibling list, this omission makes it harder for an agent to choose correctly.

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