anim_add_branching_point

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the tool adds a branching point and has a save flag, but it does not explain side effects on the montage, whether the edit is saved immediately by default, what happens if the branch already exists, or what asset state is required.

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 compact and well organized: one purpose sentence, a short Args block, a KB pointer, and a two-argument example. No filler sentences are present, and the use case is 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?

With an output schema present, return-value details are not required, and the example plus KB pointer help ground the call. But for a mutating 6-parameter tool with no annotations, the prose does too little to explain the branching-point model, how notify_type affects the result, or what happens on failure; an agent would likely need the KB reference.

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 docstring Args list is the only place an agent learns parameter meaning. It does add value: time is in seconds, notify_type has an allowed-value hint, and save is explained as saving after editing. However, several entries merely restate their names, and notify_state_duration lacks units/behavior beyond 'duration'.

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 first sentence names the exact operation ('Add a Montage Branching Point') and distinguishes the backing implementation ('backed by a branching AnimNotify event'). This is more specific than the bare tool name, though it doesn't contrast with adjacent animation tools like anim_add_anim_notify or anim_add_montage_slot.

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 implies its use through purpose and the Args list, and points to a KB section for animation-system context. But it does not state when to prefer this over anim_add_anim_notify or other montage mutation tools, nor does it give any exclusions or prerequisites such as montage must already exist.

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