set_anim_curve_color

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

Even though annotations cover the mutation/idempotency profile, the description adds substantial behavior: one undo step, package save, error-on-wrong-curve-type semantics, the applied=false/saved=false no-op result, and the failed-save branch. This is far richer than the annotations alone.

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?

One dense but front-loaded block: purpose and cosmetic caveat first, then constraints, then no-op behavior, then the return shape. Every clause carries distinct information with no filler.

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?

Despite having no output schema, the description inlines the full return object (applied, saved, save_error, message) and explains each observable outcome. Nothing needed to invoke or interpret results is missing for a single-mutation 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 coverage is 100% so the color format (RGBA 0..1) is already documented, giving a baseline of 3. The description adds a real constraint on curve_name (must be a float curve, transform curves error out), which is semantics beyond the schema.

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 precise verb and resource: the editor display color of a FLOAT curve on a UAnimSequence, and immediately flags it as cosmetic. It is clearly distinguishable from siblings like set_anim_curve_keys, set_anim_curve_interp_mode, and rename_anim_curve without opening a 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?

Gives an explicit applicability condition (FLOAT-curve only; transform curves are an error) and describes the no-op case (color already set). It does not name a specific alternative tool to use instead, but the guardrails make when-to-use clear.

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