set_cdl

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

With no annotations, description carries full burden. It mentions only provided values are changed (non-destructive merging), but lacks disclosure of side effects, permissions, or idempotency. Minimal behavioral context beyond the mutation hint.

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 compact with clear sections (intro, optional note, args list). No redundant sentences; every part adds value.

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?

Explains parameters well but omits return value (despite having output schema), interaction with session state, and relationship to siblings. Adequate for a straightforward setter but could provide more system context.

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%, but description adds meaning by explaining each param (e.g., 'RGB slope values [r, g, b]'). Saturation description is vague ('Global saturation value'), but overall compensates for lack of schema descriptions.

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?

Clearly states 'Set CDL (Color Decision List) values', specifying verb and resource. However, lacks explicit differentiation from sibling tools like set_saturation or set_lut, though CDL context is unique.

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?

States 'All parameters are optional — only provided values are changed', giving clear usage pattern. But does not specify when not to use, prerequisites (e.g., needing a session), or compare with siblings.

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