DaVinci Resolve MCP Server

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

With no annotations provided, the description carries full burden but offers limited behavioral disclosure. It mentions creation but doesn't cover permissions needed, whether it's destructive to existing nodes, error handling, or what 'connected' means operationally. The return message is vaguely described as 'success or failure' without detailing format or content.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value: the first states the action, and the subsequent lines document parameters and return values without redundancy or fluff.

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 (creating multiple nodes with connections), no annotations, and an output schema present (though unspecified), the description is moderately complete. It covers the basic purpose and parameter structure but lacks behavioral details, error conditions, and sibling differentiation that would be needed for higher completeness.

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 significant value beyond the schema, which has 0% coverage. It explains that 'node_chain' is a list of dictionaries with 'type', optional 'name', and optional 'params', providing essential semantics missing from the bare schema. However, it doesn't specify allowed node types or param structures, leaving some ambiguity.

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 action ('Create a chain of connected Fusion nodes') and the resource ('in the current composition'), providing specific verb+resource information. However, it doesn't explicitly differentiate from sibling tools like 'create_fusion_node' (singular vs. chain), which would be needed for a perfect score.

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 like 'create_fusion_node' or other creation tools. There's no mention of prerequisites, use cases, or exclusions, leaving the agent with minimal context for tool selection.

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