anim_create_nla_strip

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

Annotations contain no safety hints, so the description carries the full behavioral disclosure burden. 'Push action to NLA' hints at a move-like behavior, but it does not clarify whether the original action is removed, whether an existing strip is overwritten, or what side effects occur. With no readOnly/destructive annotations, this leaves important behavior unexplained.

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 concise: two short sentences with no filler. The core action is front-loaded and the added looping hint is relevant. It could be slightly clearer about exactly where the suffix applies, but overall it is efficiently structured.

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?

For a tool with three parameters, no output schema, and no safety annotations, this description is too sparse. It omits the semantics of the required object_name and frame_start, and does not explain what 'push' does to the source action. The tool may be simple, but the missing information creates avoidable ambiguity for the agent.

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 for the undocumented parameters. It implicitly suggests the strip_name convention via the '-loop suffix' hint, but it does not explain the required object_name parameter or the meaning of frame_start, leaving the agent to guess their roles.

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 states a specific action ('Push action to NLA') and a clear target resource, which matches the tool's name and title. It does not explicitly distinguish itself from siblings like anim_create_action or anim_assign_action, but the NLA focus is unambiguous enough for an agent to grasp the core purpose.

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 an explicit naming convention ('Use -loop suffix for Godot looping'), which is useful conditional guidance. However, it does not explain when to use this tool instead of related animation tools such as anim_create_action or anim_assign_action, nor does it state prerequisites like having an action selected or created first.

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