godot_create_animation

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

Annotations indicate this is a mutation tool (readOnlyHint=false) but do not disclose further behavioral traits. The description adds no extra context such as overwrite behavior, persistence via save_path, or side effects on the scene. It does not contradict the annotations, but it contributes minimally beyond what the schema already exposes.

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 with no redundancy. It is front-loaded and efficiently states the core action without wasting words. It is appropriately sized for the information conveyed.

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?

The tool is complex, with nested structures for tracks and keyframes, multiple enum types, and optional save/insert paths. The description only provides a terse overview and does not explain how to structure the input, when to use it, or what the expected outcome is. Despite a rich schema and output schema, the description leaves significant gaps for the agent to discover.

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?

The schema description coverage is 0%, meaning the tool description does not explain any parameters. Although the schema itself contains detailed descriptions for fields like tracks, keyframes, and save_path, the description fails to compensate for the low coverage. It offers no additional semantic meaning or usage guidance for the parameters.

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 tool 'Create or modify tracks and keyframes in an AnimationPlayer.' It names a specific resource (AnimationPlayer) and action (create/modify tracks and keyframes), making the purpose evident. However, it does not explicitly distinguish this from other animation-related tools like godot_configure_animation_tree, so it falls short of a 5.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, typical use cases, or recommend this tool over others like godot_configure_animation_tree. The agent must infer usage from the tool name and schema alone.

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