Create preset morph

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses a rich set of behavioral traits: snapshotting into slots, internal normalization of weights, use of Lag CHOP + Lookup curve, exposure on a Null CHOP for bind_to_channel consumers, and the paused-timeline limitation. This goes far beyond what annotations provide and helps the agent anticipate side effects and constraints.

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 front-loaded with the core concept and uses four dense sentences that each carry substantive information. It is appropriately sized for the tool's complexity, though it packs many technical terms into a compact space. No filler or redundant phrasing.

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 the tool's complexity (10 params, nested objects, no output schema), the description gives a strong conceptual and architectural overview, including key limitations. However, it does not explicitly state what the tool returns (e.g., path/status), which is a minor completeness gap for an agent expecting to consume the result. Still, the volume of contextual detail is high.

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 input schema covers 100% of parameters with detailed inline descriptions, so the baseline is 3. The description adds contextual architecture (Lag CHOP, Lookup curve, Null CHOP) but does not add new per-parameter meanings beyond what the schema already states. It reinforces the overall workflow but doesn't elevate parameter understanding further.

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 opens with 'Target-agnostic preset morph engine' and immediately specifies the resource (any OP's animatable parameters), the action (snapshot into N named slots, blend with weight vector or A↔B recall), and the output (exposed on a Null CHOP). It distinctly differentiates from create_look_bank by contrasting scope and weight-count support, making the tool's purpose unmistakable.

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 explicitly names create_look_bank as an alternative and clarifies when this tool is appropriate ('Unlike create_look_bank … this drives any OP and supports >2 simultaneous weights'). It also points to reuse of manage_cue's MORPH_HOOK for quantized recall, and adds a critical caveat about Lag CHOP not advancing while the timeline is paused, effectively giving both when-to-use and when-not-to-use guidance.

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