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 the tool executes code and returns results, but lacks critical details: it doesn't specify security implications (e.g., sandboxing, permissions), side effects (e.g., modifying Resolve state), error handling, or execution environment constraints. For a tool that runs arbitrary code with no annotation coverage, this is a significant gap.

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: a clear purpose statement followed by brief 'Args' and 'Returns' sections. Every sentence earns its place without redundancy, making it easy to scan and understand quickly.

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 arbitrary code) and the presence of an output schema (which handles return values), the description is minimally complete. It covers the basic action and parameter but lacks safety warnings, execution context, or integration details with DaVinci Resolve. With no annotations and high-stakes behavior, it should provide more guidance to be fully adequate.

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 explains that the 'code' parameter is 'The Python code to execute,' which clarifies its purpose, but the schema already documents it as a required string with 0% description coverage. Since there's only one parameter and the description provides basic context, it meets the baseline for adequate but not comprehensive 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 purpose: 'Execute arbitrary Python code in DaVinci Resolve.' It specifies the verb ('Execute'), resource ('Python code'), and context ('in DaVinci Resolve'), which distinguishes it from generic Python execution tools. However, it doesn't explicitly differentiate from its sibling 'execute_lua', which has a similar pattern but for Lua code.

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 sibling tools like 'execute_lua' for Lua code or other execution methods, nor does it specify prerequisites, use cases, or exclusions. The agent must infer usage from the tool name and context alone.

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