DaVinci Resolve MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool executes a Lua script and returns the result, but it lacks details on permissions required, potential side effects (e.g., whether it modifies project state), error handling, or execution limits. For a tool that likely interacts with a complex system like DaVinci Resolve, this is a significant gap in transparency.

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 highly concise and well-structured, consisting of two brief sentences that state the purpose and outline parameters and returns. Every sentence earns its place without redundancy, making it efficient and front-loaded for quick understanding.

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 tool's complexity (executing scripts in a professional software environment) and the presence of an output schema (which handles return values), the description is partially complete. It covers the basic action but lacks context on integration with DaVinci Resolve, error scenarios, or behavioral nuances. With no annotations and minimal parameter guidance, it meets a minimum viable level but has clear gaps.

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 minimal semantics beyond the input schema. It defines the 'script' parameter as 'The Lua script to execute,' which clarifies the content but doesn't provide examples, syntax requirements, or constraints. With 0% schema description coverage, the description partially compensates but doesn't fully address the lack of schema details, resulting in a baseline score.

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 purpose: 'Execute a Lua script in DaVinci Resolve's Fusion.' This specifies the verb ('execute'), resource ('Lua script'), and context ('DaVinci Resolve's Fusion'), which is clear and specific. However, it doesn't explicitly differentiate from sibling tools like 'execute_python', which performs a similar function but with a different scripting language.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose Lua over Python (via 'execute_python') or other scripting options, nor does it specify prerequisites, contexts, or exclusions for its use. This leaves the agent without explicit usage instructions.

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