resolve_apply_lut

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

Annotations (idempotentHint=true, readOnlyHint=false, destructiveHint=false) are consistent. Description adds detail about one-based color node indexing and allowed LUT constraint, providing context beyond annotations.

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 of 14 words is concise and front-loaded. However, the brevity sacrifices essential details that could be included without verbosity.

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?

Missing critical context: no explanation of output, error handling, prerequisites (e.g., timeline open, items selected), or behavior when item_ids or node_index are invalid. Has output schema but description does not hint at return format.

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 description coverage is 0%, so description must compensate. Only lut_path and node_index are partially explained via the description; item_ids, timeline_id, and timeline_name are not described. Important parameters lack semantic context.

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 verb 'Apply', resource 'allowed local LUT file', and target 'to a one-based color node on selected timeline items'. This specific verb+resource+target distinguishes from sibling tools like resolve_edit_items or resolve_configure_render.

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?

Implies usage context (items must be selected, LUT must be allowed) but does not explicitly state when to use this tool vs alternatives. No exclusions or alternative tools mentioned.

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