imgui_stop_all_animations

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

No annotations are provided, so the description carries full burden. It does disclose that this removes all animations (a destructive/bulk action with no undo), which is valuable context. However, it doesn't mention side effects on ongoing UI state or whether this affects animation-linked callbacks/timers.

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?

A single sentence that fully conveys action, scope, and effect with zero waste. Every word earns its place.

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?

For a zero-parameter tool with no output schema, the description is reasonably complete. It conveys the destructive bulk nature clearly. However, given the irreversibility (removes animations permanently), some note about confirmation or behavioral impact would strengthen 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 word 'all' in the description adds semantic meaning going beyond the schema. With 0 parameters, the schema provides no information, so the description's scoping clarification ('across all windows') is the only meaningful parameter-level semantics available. Baseline 4 applies for 0-param tools.

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 ('stop and remove') and resource ('all active animations across all windows'), distinguishing it from sibling imgui_stop_animation which stops a single animation. It's specific about scope and action.

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 implies a bulk operation ('all active animations'), which contrasts with sibling imgui_stop_animation (single animation), but it doesn't explicitly say when to use this tool vs alternatives. No explicit when/what-not guidance is provided.

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