GSAP MorphSVG

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

No annotations are provided, so the description carries the full burden. It only mentions input type requirements (SVG path elements or data strings) but does not disclose side effects, DOM modifications, or error handling. This is a significant gap.

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-loading the core purpose and a usage hint. Every sentence is valuable and there is no waste.

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?

With 7 parameters, low schema coverage, no output schema, and no annotations, the description is too minimal. It fails to explain the complex options object or other parameters, making it incomplete for an agent.

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 low (29%), and the description adds no parameter-specific semantics beyond mentioning target and endShape. Parameters like ease, duration, options, useTimeline, includeImports remain unexplained.

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?

Description clearly states it morphs one SVG path into another using MorphSVGPlugin, specifying the required inputs (target and endShape) and their types. It distinguishes from gsap_drawsvg, aiding correct tool selection.

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?

Description provides an explicit alternative (gsap_drawsvg) for drawing SVG strokes, but does not elaborate on when to use morphsvg vs other sibling tools like gsap_motionpath or gsap_flip. The context is implied but limited.

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