davinci_resolve

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 names 'requires Resolve to be running' but doesn't explain that the tool is effectively a dispatcher that requires a valid 'action' parameter, what side effects mutating actions have, whether actions persist state, or what happens on errors (e.g., when Resolve isn't installed on the host). The broad action list implies mutating capabilities (render, delete, add) but nothing is disclosed about their effects or reversibility.

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 short and the action list is front-loaded, which is structurally reasonable. However, the list of 38 action names is essentially just a flattened enum dump that duplicates what the 'action' parameter's enum already provides. It's not redundant bloat, but it doesn't add meaningful structure; it reads like a copy-paste of the enum values.

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?

This is a highly complex tool with 41 parameters, 38 actions, no annotations, and no output schema. The description is far from complete: it doesn't explain parameter-to-action relationships, expected outputs, required parameters per action, or error modes. For a dispatcher tool of this complexity, the description should map actions to their relevant parameters or at least group related actions. This fails to meet that bar.

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?

Schema coverage is 100%, so each of the 40 optional parameters has a description in the schema. However, the description adds essentially no semantic value beyond the schema - it simply lists action names. Critically, since this is a dispatcher pattern, the description does nothing to clarify WHICH parameters apply to WHICH actions. Given 41 parameters and 38 possible actions, this is a severe gap that the schema alone cannot bridge.

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 states the tool controls DaVinci Resolve Studio via scripting API and lists 38 actions. It names a specific resource (DaVinci Resolve) and verb (Control), but is essentially a mega-tool covering dozens of unrelated operations (render, markers, subtitles, timecode, media import). The action list gives some specificity but no single clear purpose; it reads more like a navigation menu than a focused tool definition.

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 only usage guidance is 'Requires Resolve to be running', which is a prerequisite rather than guidance on when to use this tool vs alternatives. With 38 sibling tools present, there is no mention of when this tool is preferred, when not to use it, or how the 38 different actions should be selected. No exclusions or alternative recommendations are given.

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