davinci_list_luts

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

No annotations are present, so the description carries the full burden of behavioral disclosure. The verb 'Lists' strongly implies a non-destructive read operation, and 'currently installed' conveys a snapshot of current state. However, it does not explicitly state that no modifications occur, whether DaVinci Resolve must be running, or any potential side effects.

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?

A single, tightly worded sentence that front-loads the action ('Lists') and includes all essential scope details without filler. Every word earns its place.

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?

The description covers the core purpose and scope fully. With an output schema present, return values are presumably defined elsewhere. The only missing context is an explicit statement about when to use this versus applying or generating LUTs, but for a simple list operation the definition is largely complete.

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 tool has zero parameters, so there is nothing for the description to explain beyond the schema. The baseline for 0-parameter tools is 4, and the description adds no unnecessary parameter information.

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 uses a specific verb ('Lists'), a specific resource ('Antigravity LUTs'), and a precise location ('DaVinci Resolve's native system directory'). This clearly distinguishes it from sibling tools like davinci_apply_lut and davinci_generate_and_install_lut, which perform different actions on LUTs.

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 usage context is implied: use this tool to discover installed LUTs. However, it does not explicitly mention when to choose this over alternatives or any exclusions, such as 'use apply_lut to apply a LUT' or 'use generate_and_install_lut to create one.' No alternative routing is provided.

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