set_color_ramp_interpolation

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

With no annotations, the description carries full burden. It explains the main effect (set interpolation and color_mode) and return value, but does not disclose prerequisites (e.g., material/node must exist), error behavior, or side effects. Acceptable but could be more transparent.

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?

Description is concise and well-structured: main action first, then usage examples, then a clean args list. Every sentence adds value without redundancy.

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 moderate complexity and presence of an output schema (though not fully shown), the description covers all parameters and return value. It could mention that material and node must exist, but overall it is sufficiently complete for an agent.

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 0%, so description compensates well. It provides clear meaning for each parameter: material_name, node_name, interpolation (with specific options), and color_mode (optional, with RGB/HSV/HSL listed). Adds value 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?

The description clearly states 'Set how a ColorRamp blends between its stops', a specific verb and resource. It distinguishes from sibling tools by focusing on ColorRamp interpolation and color mode adjustment.

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 provides guidance on when to use each interpolation type (e.g., CONSTANT for hard edges, EASE/B_SPLINE for softer falloff) and explains color_mode's purpose. It lacks explicit when-not-to-use or alternative tools, but the context is clear.

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