set_particle_color_gradient

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 explains the action (build and assign) but does not mention side effects, prerequisites (e.g., a valid node_path with a particle material), color format expectations, or whether existing gradients are replaced. For a mutating tool, this is insufficient detail.

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 a single, front-loaded sentence that directly states the tool's purpose without wasted words. It is appropriately concise and easy to scan.

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 has no annotations, no output schema, and zero schema description coverage, the description is not complete enough. An AI agent would lack crucial details about color value formats, allowed offset ranges, potential errors, and exactly how the gradient is applied to the material. The tool is simple, but the description still leaves significant gaps for safe and correct invocation.

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. It adds meaning to 'stops' by specifying they are 'ordered offset/color stops' and that a 'color ramp' is built, which clarifies the relationship between the two parameters. However, it does not explain the color string format, offset range, or node_path semantics beyond what the schema already shows.

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 clearly states the tool's function with specific verbs ('Build' and 'assign') and identifies the resource ('particle material'). It distinguishes from sibling tools like set_particle_material by focusing specifically on building a gradient from color stops, which is a unique capability among the listed particle tools.

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 does not provide any guidance on when to use this tool versus alternatives such as set_particle_material or apply_particle_preset. It implies usage for creating color ramps, but there is no explicit context, exclusions, or comparisons to related tools.

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