color_export_lut

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

No annotations are present, so the description must disclose behavior on its own. It does not mention side effects (e.g., file creation/overwriting), permission needs, or any preconditions beyond the schema. This is a minimal statement of action with no transparency beyond the verb.

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 with no wasted words. It efficiently communicates the core function.

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 high schema coverage and presence of an output schema, the core invocation is understandable. However, the lack of usage guidelines and behavioral context leaves gaps about when to use it and what side effects to expect, so completeness is only adequate.

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?

All five parameters are documented in the schema with descriptions, so the baseline is 3. The description does not add parameter-level detail, but it does contextualize 'combined grade' as the data being exported. The schema still carries the burden for parameter semantics.

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 a specific action ('Export') and a specific resource ('combined grade of a timeline item') with an explicit output format ('LUT file'). It reads distinctly from sibling color tools like color_get_lut/color_set_lut, which focus on reading/setting LUTs rather than exporting a file.

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 offers no guidance on when to choose this tool over similar color tools, nor does it mention prerequisites or alternatives. It simply states the action, leaving the agent to infer usage context.

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