set_color_label

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

Annotations provide no behavioral hints beyond readOnly=false. Description adds no additional behavioral details: e.g., whether the label overwrites existing, affects clips in sequences, requires item to be unlocked, or has any side effects on associated items.

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?

Single sentence, no wasted words, action clearly front-loaded. However, lacks any structure (e.g., bullet points) that could aid readability, though not detrimental.

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?

Minimally adequate for a simple setter: no output schema, but description does not mention return behavior or side effects. Context within video editing domain is implied but not explicit.

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 100%, with both parameters described. The description of color_index enumerates all color-index mappings. However, the tool description itself adds no extra semantic value beyond what the schema already provides.

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?

Description clearly states action: 'Set the color label on a project item or clip.' Verb (set) and resource (color label) are specific. Distinguishes from 'get_color_label' and 'set_color_value' siblings by targeting 'color label' rather than 'color value'.

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 on when to use this tool versus alternatives like 'set_color_value' or 'get_color_label'. No context about prerequisites, typical use cases, or scenarios where other tools are preferred.

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