add_animation_track

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and gives an example, but does not disclose side effects (e.g., whether it modifies the animation resource in place), prerequisites (e.g., whether the animation must already exist), or behavior for different track types.

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, well-structured sentence that front-loads the action and includes a concrete example. There is no wasted text, and the most important information is immediately accessible.

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 5 parameters, 2 enums, no annotations, and no output schema, the description is insufficient. It only covers the path context and omits crucial details about track_type options, update_mode semantics, and how node_path relates to track_path. An agent would need additional knowledge to use this tool correctly.

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 gives an example of the path format ('Sprite2D:position') but does not explicitly explain the roles of node_path vs. track_path, nor does it cover track_type or update_mode. This leaves significant ambiguity about 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 action ('Append a track to an animation') and specifies the target ('a node property path relative to the AnimationPlayer root node'), with a concrete example ('Sprite2D:position'). This distinguishes it from sibling tools like set_animation_keyframe or get_animation_info, which serve different purposes.

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 clear context: this tool is for appending tracks, and shows the expected path format relative to the AnimationPlayer. However, it does not explicitly mention alternatives or exclusions (e.g., when to use set_animation_keyframe instead), leaving the differentiation to inference.

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