GSAP Debug Helper

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

With no annotations provided, the description carries full burden and thoroughly explains each mode's behavior: visualize enables markers and logging, gsdevtools requires Club GSAP membership, log tracks progress/time, slowmo scales global timeline speed, and labelDump prints labels. It also warns about production cleanup.

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: one paragraph efficiently lists modes with brief explanations and ends with a critical usage guideline. Every sentence adds value, and there is no redundancy.

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 description covers purpose, usage, and behavioral details adequately for a debug tool, but lacks explicit mention of output format (e.g., generated code snippets). With no output schema, some additional context about return values would improve completeness.

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 description adds value by explaining the action modes beyond the schema's enum listing, but does not elaborate on the 'target' or 'options' parameters. Given schema description coverage is 67%, the description partially compensates with action details, justifying a score of 4.

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 debugging utilities for GSAP animations, listing specific modes (visualize, gsdevtools, log, slowmo, labelDump) with brief explanations. It distinguishes itself from sibling tools by focusing on development-specific debugging actions.

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 explicitly advises using this tool only during development and removing debug code before production, providing clear when-to-use guidance. However, it does not directly contrast with siblings like gsap_analyze or gsap_performance, which could be considered related.

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