gsap-stagger

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

With no annotations, the description must disclose behavioral traits, but it only states the function. It does not mention that the tool applies animations with delays to multiple elements, the need for a selector matching many elements, or any side effects. The description is insufficient for transparency.

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 extremely short (two words), which is concise but lacks structure. It is front-loaded with the purpose, but the brevity leaves out important context such as parameter use cases. Every word earns its place, but more could be added without sacrificing 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 simplicity, the description is incomplete. It omits the fact that the tool expects a CSS selector and a stagger delay, and does not mention return values or behavioral constraints. With no output schema, the description should at least hint at the effect or result.

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 coverage is 100% with descriptions for both parameters (selector and stagger). The tool description adds no additional meaning beyond the schema, but the schema already provides adequate parameter info, so baseline of 3 is appropriate.

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 'Create staggered animations' clearly states the tool's function with a specific verb and resource (staggered animations). It distinguishes from generic animation tools like gsap-animate by focusing on staggering, but does not explicitly differentiate from other stagger-related tools.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like gsap-animate or gsap-easing, missing an opportunity to guide the agent.

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