cdl_set

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

The description does not disclose behavioral traits beyond the basic operation. With no annotations, it fails to mention side effects (e.g., overwrites existing CDL, creates new node), error handling, or reversibility. The agent lacks critical context for safe invocation.

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 short sentences with no redundancy. Every word serves a purpose. Ideal length for this level of detail.

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?

The tool has 6 parameters and no output schema or annotations, yet the description is extremely brief. It does not explain return values, prerequisites, common use cases, or how it interacts with the node graph. For a tool modifying color data, this is insufficient.

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 description adds meaning for three parameters (slope, offset, power) by explaining they are three numbers each. However, it omits the other three parameters (node_index, saturation, item_handle), and the schema has no descriptions (0% coverage). Only partial improvement over 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 the tool applies ASC CDL values to a node, naming the three components (slope, offset, power) and noting each is three numbers. This specific verb and resource distinguish it from siblings like 'lut_apply' or 'grade_copy'.

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?

No guidance is given on when to use this tool versus alternatives such as 'lut_apply', 'grade_copy', or manual grading. There is no mention of prerequisites, conditions, or when not to use it.

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