create_animation

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely says 'create an empty' resource but does not explain potential side effects, whether an existing animation is overwritten, dependencies on nodePath, or any required scene setup. The behavior remains opaque.

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, non-redundant sentence that is easy to scan. It avoids fluff, but it is somewhat under-specified given the tool's five parameters. Still, it is concise and front-loaded.

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?

This is a mutation tool with 5 parameters, no annotations, and no output schema. The description does not explain prerequisites (e.g., existing AnimationPlayer), return values, or how length and nodePath affect the creation. Given the complexity, the description is insufficient for reliable invocation.

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 only 20% (only projectPath has a description). The tool description adds no parameter details, so the agent must rely on parameter names. Ambiguities like nodePath default '.' and length default 1 are not explained, and the purpose of scenePath vs projectPath is unclear.

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 action (create), the resource type (empty AnimationPlayer animation resource), and the target context (in a scene). This is specific and distinguishes it from sibling tools like create_scene (creates scene) and inspect_animation_players (inspects).

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 gives no guidance on when to use this tool versus alternatives, nor any prerequisites such as requiring an existing AnimationPlayer node. It does not mention exclusions or conditions, leaving the agent to infer usage from the parameter names.

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