add_notify_track

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

Despite annotations already covering the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description goes well beyond them: it discloses that the edit runs in an undo transaction and is saved, that a duplicate track name is a success with already_existed=true and nothing written, and that a failed save yields success=false, saved=false and save_error. That is exactly the post-condition detail an agent needs for a mutation.

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?

Two front-loaded sentences plus a compact Returns line. The scoping caveat comes first, the edge-case semantics second, and the return shape last; no sentence is redundant or padded.

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?

No output schema exists, and the description compensates by enumerating every returned field (including track_names/track_count for verification) and the success/failure contract. Combined with the fully-covered input schema, an agent has everything needed to call and interpret this tool.

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 100%, so all three parameters (animation_path, track_name, color) are already documented in the schema; the description adds scope meaning to track_name ('the track, not events on it') but says nothing about color or path format. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (add) plus a precisely-scoped resource (a named notify TRACK on a UAnimSequence), and explicitly disambiguates from the event-level siblings: 'the track itself, not events on it'. An agent can distinguish it from add_anim_notify / add_montage_notify without opening either schema.

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 parenthetical scoping tells the agent when this tool is correct versus adding notify events, which is genuine routing guidance against a very dense sibling set. However it never names the alternative tool explicitly nor states when-not to use it (e.g. track already exists → prefer get_notify_track_names / remove_notify_track), so it stops short of a full when/when-not statement.

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