manage_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 adds useful semantics (create must not invent IDs, load does not play, get_tracks returns tracks on a rig), but it does not describe effects of stop/stop_all, required prerequisites, or return behavior, leaving significant gaps.

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 compact sentences with a clear, inline action list. It front-loads the key caveat about animation IDs and avoids wasted words, achieving high density of useful information.

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 6-parameter, multi-action tool with no annotations and no output schema, the description is too thin. It doesn't clarify which parameters each action requires, what stop_all affects (global vs. per-rig), or what each action returns, making it incomplete for an agent to invoke correctly in all cases.

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 only 33%, so the description must compensate. It adds context for animationId (do not invent), implies rigPath via 'load onto a rig', and clarifies get_tracks is rig-based, but leaves name, parentPath, and the precise semantics of path only partially covered.

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 explicitly names the resource (animations) and enumerates seven concrete actions (create, list, load, play, stop, stop_all, get_tracks), making the tool's purpose specific and distinguishing it from sibling tools like manage_audio or manage_camera.

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?

There is no explicit guidance on when to use this tool versus alternatives, but the action list and resource name make the primary use case clear. The note about preferring user-provided or search-accepted animation IDs is helpful, but no exclusions or sibling alternatives are mentioned.

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