animation_create

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

With no annotations, the description carries the burden of disclosing behavior. It reveals two non-obvious traits: auto-creation of the AnimationPlayer when player_path is unresolved, and that track node paths are relative to the AnimationPlayer's root_node. It doesn't cover error behavior or side effects when overwrite=false, but the disclosed behaviors are significant and useful.

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 three sentences, each earning its place: creation purpose, workflow follow-up, and auto-creation detail. It is front-loaded and free of filler, making it easy to parse quickly.

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 tool's complexity and the presence of a complete input schema and output schema, the description covers all essential context: where the clip is created, how to proceed with tracks, path handling subtleties, and auto-creation behavior. No critical behavioral or contextual gaps remain.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining auto-creation for player_path and clarifying that node paths are relative to root_node, which affects how parameters like player_path and name are interpreted. This contextual info is not present in the schema, so the description adds value.

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 begins with a specific verb+resource+location: 'Create a new Animation clip inside an AnimationPlayer's default library.' It clearly distinguishes from sibling tools like animation_manage by explicitly directing track-manipulation follow-up to that tool, making the purpose unmistakable.

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 explicit workflow guidance: after creating the clip, add tracks via animation_manage ops. It also gives an alternative ('see animation_manage preset ops for a forgiving target_path') and explains auto-creation behavior when player_path doesn't resolve, covering both when and how to use the tool.

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