create_animation_player

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

Annotations already indicate this is a mutating operation (readOnlyHint=false), and the description adds the optional animations behavior. However, it does not disclose deeper behavioral details such as what happens if the node already exists, whether the scene file is saved, or prerequisites like project/scene validity.

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?

Two concise sentences with the primary action front-loaded and no redundant filler. Every clause contributes meaning, including the alternative tool pointer.

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 schema coverage and the explicit sibling differentiation, the description is sufficiently complete for a creation tool. It could optionally mention side effects like saving the scene or handling existing nodes, but those are not critical given the schema and annotations.

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 covers 100% of parameters, so the baseline is 3. The description adds only minimal extra context by calling animations 'optional pre-configured animations', which aligns with the schema but does not elaborate on structure or defaults beyond what the schema already provides.

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?

Description clearly states it creates an AnimationPlayer node in a scene with optional pre-configured animations. It explicitly distinguishes itself from add_animation, which is for adding animations to an existing player.

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?

Provides explicit guidance on when not to use this tool by directing users to add_animation for existing players. This gives clear contextual differentiation among sibling tools.

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