creator_stop_animation

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Stop all animations' but does not explain side effects, reversibility, or what happens to the animation timeline or keyframes. The parameter 'immediate' hints at lead-out behavior, but the description itself adds no detail.

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, direct sentence with no waste. However, it is slightly under-specified for a tool that has relevant sibling tools and a parameter that affects behavior, so it does not earn a 5.

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 presence of sibling tools with overlapping functionality (pause, seek, play), the description is too minimal for an agent to confidently select this tool. It lacks details about the 'stop' semantics, consequences, and difference from pause, making it incomplete in context.

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 100% (the 'immediate' parameter is described as 'Skip lead-out (default true)'). The description text adds nothing beyond the schema, so the baseline score of 3 applies—schema does the heavy lifting.

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 'Stop all animations.' specifies the verb (stop), resource (animations), and scope (all), making the core purpose clear. It does not explicitly distinguish from sibling tools like pause_animation, but the scope is evident.

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 no guidance on when to use this tool versus alternatives (e.g., pause_animation, seek_animation). It lacks any context about appropriate scenarios or exclusions, leaving the agent without selection criteria.

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