search_and_apply_lut

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

With no annotations, the description must fully disclose behavior. It mentions searching recursively and applying to optional clip and node indices, but does not describe error handling (e.g., LUT not found), side effects (overwriting existing LUT), or the specific standard directories. This is adequate but not comprehensive.

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 concise with a front-loaded purpose sentence followed by structured parameter details. No redundant information. Every sentence 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?

Given the complexity of searching and applying a LUT, the description covers the core behavior but misses details like the exact search path, supported file formats, and error handling. The existence of an output schema reduces the need to explain return values, but more context would improve completeness for an agent.

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 beyond the schema titles by explaining 'lut_name' as a filename, 'clip_index' as a 1-based index on video track 1, and 'node_index' with a default of 2. It also provides an example for lut_name. This compensates for the 0% schema description coverage.

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's action: 'Search standard LUT directories for a LUT file by name and apply it.' It specifies the resource (LUT) and the verb (search and apply), and distinguishes from the sibling tool 'set_lut' which likely applies a LUT without a search step.

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 does not provide any guidance on when to use this tool vs. alternatives like 'set_lut'. There is no mention of prerequisites, or when not to use it, which is essential for an agent to choose correctly among similar tools.

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