create_animation

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

With no annotations provided, the description carries the full transparency burden. It fails to disclose whether an existing animation with the same name is overwritten, whether the default library is auto-created, or what happens if the AnimationPlayer path is invalid. For a mutation tool, these side effects and prerequisites are critical.

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 sentence that is front-loaded with the core action and includes essential parameter details inline. It is efficient and free of unnecessary words.

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 no annotations or output schema, the description should provide more context about side effects and prerequisites. It covers the purpose and two parameters but omits overwrite behavior, error handling, and requirements for the node path, making it incomplete for a creation tool.

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 0%, so the description must compensate. It adds meaning for length ('in seconds') and loop_mode ('0 none, 1 linear, 2 pingpong'), but leaves node_path and name to be inferred from the tool's purpose. This partial coverage falls short of fully compensating for the lack of schema descriptions.

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 uses the specific verb 'Create' with a clear resource ('empty Animation') and container ('AnimationPlayer's default library'), clearly distinguishing it from sibling tools like add_animation_track or set_animation_keyframe. It also specifies the key attributes (length, loop mode).

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 usage for initializing an empty animation before adding tracks or keyframes, but it doesn't explicitly state when to use this tool vs siblings, nor does it mention alternatives or exclusions. The context is clear but the guidance is only implicit.

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